Rename npm packages with scoped names
See original GitHub issuehttps://docs.npmjs.com/getting-started/scoped-packages
Instead of having https://www.npmjs.com/~babylonjs we can have scoped npm package names:
Examples of the scoped name change:
babylonjs
->@babylonjs/core
babylonjs-inspector
->@babylonjs/inspector
babylonjs-materials
->@babylonjs/materials
babylonjs-loaders
->@babylonjs/loaders
That will prove that all @babylonjs
packages are official ones 😉
More informations https://babeljs.io/blog/2017/12/27/nearing-the-7.0-release#renames-scoped-packages-babel-x
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:18 (17 by maintainers)
Top Results From Across the Web
npm - Understanding Scoped Packages - Nitay Neeman's Blog
One of the mandatory fields that an npm package must have is a name: "name": "sample-package". The name should be unique, ...
Read more >scope - npm Docs
All npm packages have a name. Some package names also have a scope. A scope follows the usual rules for package names (URL-safe...
Read more >How to migrate NPM package to an organization @scope
Another way to do this that doesn't involve renaming the package, is to go to the team settings in ...
Read more >Best practices for creating a modern npm package - Snyk
You will first learn how to create an npm package, so you can get familiar ... Update the name property in package.json with...
Read more >Scope hoisting - Parcel
In addition, imported variables are renamed to match the exported variable names from the resolved module. Finally, any unused exports are removed.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Shipped : https://doc.babylonjs.com/features/npm_support#es6
But for next release (4.0) we will ship new packages for each project to support ES6 so we could start using that for them
something like @babylonjs/core-es6, @babylonjs/gui-es6, etc…
Edit: Just saw your answer 😃 So yeah definitely for the new package we could do that