-
-
Notifications
You must be signed in to change notification settings - Fork 612
Closed
Description
Below is the big-ass list of plugins that need migrating into this repo:
Done
- rollup-plugin-alias
- plugin-auto-install
- rollup-plugin-buble
- rollup-plugin-commonjs
- rollup-plugin-dsv
- rollup-plugin-image
- rollup-plugin-inject
- rollup-plugin-json
- rollup-plugin-legacy
- rollup-plugin-multi-entry
- rollup-plugin-node-resolve
- rollup-plugin-replace
- rollup-plugin-run
- rollup-plugin-strip
- rollup-plugin-sucrase
- rollup-plugin-typescript
- rollup-plugin-url
- rollup-plugin-virtual
- rollup-plugin-wasm
- rollup-plugin-yaml
Misc
- rollup-pluginutils
In Progress
- rollup-plugin-babel (in progress @Andarist)
Pending
Skip
-
rollup-starter-plugin -
rollup-plugin-butternut(deprecated in favor of terser) -
rollup-plugin-node-builtins(was an empty repo, plugin owned by third party) -
rollup-plugin-ractive(Ractive is a dead project) -
rollup-plugin-svelte(will be transferred to @sveltejs)
Before we move a plugin we should:
- Follow up on any open issues.
- Follow up on any pending Pull Requests.
- Add note to the README about the move
- Disable issues and Pull Requests
Give n number of days for response based on age of issue/PR, if there is a reproduction provided, etc.
For each plugin we should:
- Assert there are tests
- Apply linting and clean the code
- Update aged dependencies
- Remove unneeded metadata covered by the monorepo
- Create an issue label for the plugin
After moving a plugin we should:
- Put the plugin repo into an archived state
- Add a deprecation notice to the README and provide URL to the monorepo path for the plugin
- Publish a patch version with the
deprecatedproperty added to package.json.
gluons and MattiasBuelens
Metadata
Metadata
Assignees
Labels
No labels