Skip to content

Plan to put all packages under the same orngisation

Bassem AlSabbagh edited this page Mar 5, 2024 · 2 revisions

Hi, Thanks for contacting Support! We recommend flagging the non-scoped package as deprecated and declaring a code-freeze on it, while you create a new version under the **** scope: Change your package.json from: "name": "project-name" to: "name": "@responsive-ui/wetix" and publish the packageSee: https://docs.npmjs.com/getting-started/scoped-packagesNOTE: npm doesn't support redirects from old names to new names. This is a good thing, as the package adopters will make intentional decisions about moving to the new package, and you can track it's usage. Deprecate the old package with:npm deprecate pkg[@version] "message"people who install the old version would be notified that they should install another package instead.See: https://docs.npmjs.com/cli/deprecate Repeat the same steps above for @svelte-reactive-form/rules and create @wetix/rules I hope this helps. Best.JudeGitHub SupportSupporting the npm registry

Clone this wiki locally