-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
[core] Rename npm org name from @base_ui to @base-ui #488
Labels
breaking change
core
Infrastructure work going on behind the scenes
on hold
There is a blocker, we need to wait
Comments
oliviertassinari
added
status: waiting for maintainer
These issues haven't been looked at yet by a maintainer
core
Infrastructure work going on behind the scenes
breaking change
labels
Jul 24, 2024
What's the point of having this as a GitHub issue? It's not actionable, as we've already contacted npm and can only wait until they resolve this. I can see a GH issue only when we actually own the org, to update the code. |
|
michaldudak
added
on hold
There is a blocker, we need to wait
and removed
status: waiting for maintainer
These issues haven't been looked at yet by a maintainer
labels
Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking change
core
Infrastructure work going on behind the scenes
on hold
There is a blocker, we need to wait
Summary
The npm package convention is to use dash to separate words, not underscore. We used underscore
@base_ui
because we didn't find a better option.See mui/material-ui#43002 as an example of surprise:
I have flagged it as a breaking change as it's kind of one, but also doesn't have to be truly one.
Benchmark
npm packages with underscore is not common: https://github.com/evanwashere/top-npm-packages
Options
We are working on gaining access to the @base-ui npm org name. Once we get it. We should be able to migrate to it. https://www.notion.so/mui-org/ops-Trademark-Base-UI-88f653d8a8b64cac96fa7546638ecc3d?d=24e76446683d430381fdd0a65c03e3d5
The text was updated successfully, but these errors were encountered: