-
Notifications
You must be signed in to change notification settings - Fork 40
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
Heads up: upcoming change to esbuild package names #52
Comments
Thanks for the heads up, it looks straight-forward to catch up! |
I've created a draft PR for it. Rest your hands José. All the best. |
Another heads up that this change has now been released: https://github.com/evanw/esbuild/releases/tag/v0.16.0. The new package names are in the release notes. |
❤️❤️❤️🐥🔥 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a heads up that I'm planning on changing esbuild's package names in an upcoming release. The packages are being moved under the
@esbuild/
scope to avoid name collisions. I'm also changing theos
andcpu
strings to be exactly equal to the ones returned by node (previously a few of them weren't consistent). You can find the work-in-progress change that does this here: evanw/esbuild#2508.More context: I've had a problem with people trying to add support for a new platform to esbuild and then registering the package name themselves, which doesn't work because then I don't control the package name. Using a scope prevents this problem.
The text was updated successfully, but these errors were encountered: