Scoped or non-scoped package name?
See original GitHub issueSince it will probably end up being an official React integration, would you like to name it @sweetalert2/react-content
? I see it’s already published, but it’s not too late to change it.
Or better, @sweetalert2/react
or something like that, in the case you add more features.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
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 >npm - Understanding Scoped Packages - Nitay Neeman's Blog
Scoped Packages is a way to group related npm packages together, and connect them to each other by a specified “scope”, that acts...
Read more >npm - Understanding Scoped Packages - YouTube
This video explains what scopes are in regard to npm packages - focusing on how to create, publish and install them.More videos on...
Read more >npm-scope - w3resource
An unscoped package can depend on a scoped package and vice versa. Because the npm client is backward compatible with unscoped registries, you ......
Read more >How to migrate NPM package to an organization @scope
You can change your package.json from: "name": "project-name". to: "name": "@scope/project-name". and publish the package:
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 Free
Top 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
Nice idea, done! https://www.npmjs.com/org/sweetalert2
@toverux please do
@zenflow please do
Reopening since this package is almost definitely getting renamed.
We are discussing elsewhere what the name should be.
Let’s keep the “scoped vs non-scoped package name” aspect of that discussion isolated here.
I don’t have time to comment at the moment, but I will soon.