{{ message }}
Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.
I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in
一个工作流平台
A javascript template engine, simple, easy & extras, support webpack, rollup, parcel, browserify, fis and gulp
Running yarn build in the contracts package outputs a bunch of warnings.
There are no serious risks from these warnings, but we should fix them because it's easy to do, and it's easy to become desensitized to them, which results in a gradually increasing number of warnings.
Better to just pre
Template for setting up a TypeScript monorepo
A modern JavaScript|Typescript library scaffolding, modularity, purity & extras
Rollup plugin for typescript with compiler errors.
Serverless plugin for zero-config Typescript support
A project skeleton to get your very own React Component Library up and running using Rollup, Typescript, SASS + Storybook
Super fast progressive web app with small footprint & minimal dependancies
A tiny library to help load ArcGIS API for JavaScript modules in non-Dojo applications
Use ESBuild with Rollup to transform ESNext and TypeScript code.
A TypeScript Rollup plugin that bundles declarations, respects Browserslists, and enables seamless integration with transpilers such as babel and swc
Vite
when running tsc on my vite.config.ts, i get the following errors:
node_modules/rollup-plugin-chrome-extension/dist/index.d.ts:26:13 - error TS2503: Cannot find namespace 'chrome'.
26 icons?: chrome.runtime.ManifestIcons | undefined;
~~~~~~
Powerful, Flexible, Open Source dashboards for anything
Add a description, image, and links to the rollup topic page so that developers can more easily learn about it.
To associate your repository with the rollup topic, visit your repo's landing page and select "manage topics."
Current Behavior
UMD build doesn't support code-splitting and dynamic imports (rollup/rollup#3490, rollup/rollup#3491) due to Rollup current limitations, and tsdx cli don't accept the format option
amdwhen creating build configSuggested Solution
Consider support AMD module format, o