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
To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ~0.15.0.
The default in npm is caret (^) ranges. I’m not a native English speaker, but I kind of got the impression that I “should” be using a non-default range to be safe.
You probably know this, but the default caret ranges are safe too. For example, ^0.15.0 only matches 0.15.x not 0.16.x. You can try it here: https://semver.npmjs.com/
It’s also explained in the npm docs you link to (https://docs.npmjs.com/cli/v6/using-npm/semver), so astute readers could figure this out themselves too. The thing is that the caret ranges work differently for 0.x.
Maybe it’s worth mentioning that ^0.15.0 is an ok range too in the changelog to spare people not super into the details of npm some docs reading time.
Make what you will of this, and thanks for creating esbuild!
The text was updated successfully, but these errors were encountered:
Reading through https://github.com/evanw/esbuild/releases/tag/v0.16.0 I saw this:
The default in npm is caret (
^
) ranges. I’m not a native English speaker, but I kind of got the impression that I “should” be using a non-default range to be safe.You probably know this, but the default caret ranges are safe too. For example,
^0.15.0
only matches0.15.x
not0.16.x
. You can try it here: https://semver.npmjs.com/It’s also explained in the npm docs you link to (https://docs.npmjs.com/cli/v6/using-npm/semver), so astute readers could figure this out themselves too. The thing is that the caret ranges work differently for
0.x
.Maybe it’s worth mentioning that
^0.15.0
is an ok range too in the changelog to spare people not super into the details of npm some docs reading time.Make what you will of this, and thanks for creating esbuild!
The text was updated successfully, but these errors were encountered: