Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move npm packages to company scope #6

Open
2 tasks
galkin opened this issue Dec 1, 2023 · 0 comments
Open
2 tasks

Move npm packages to company scope #6

galkin opened this issue Dec 1, 2023 · 0 comments

Comments

@galkin
Copy link
Contributor

galkin commented Dec 1, 2023

Hi @hdoan741 and @huytool157, I created the issue inside this repo, but it is relevant for all company npm packages.

Today best practices for open-source npm package development recommend publishing packages under the scope. It creates better trust and simplifies naming.
Just check current package names:

  • retoolrpc
  • react-retool
  • retool-cli

Links:

Recommended actions:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant