You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the os and cpu 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:
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: