![Introducing Dashboard Analytics](https://cdn.sanity.io/images/cgdhsj6q/production/af327c5bd94708db501516a75da6870aef894c64-2286x1522.png?w=400&fit=max&auto=format)
Product
Introducing Dashboard Analytics
We're introducing a new Analytics feature in the Socket dashboard so you can view changes in your organization's and repositories' alerts over time.
@esbuild/openbsd-x64
Advanced tools
This is the OpenBSD 64-bit binary for esbuild, a JavaScript bundler and minifier. See https://github.com/evanw/esbuild for details.
0.20.0
This release deliberately contains backwards-incompatible changes. 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.19.0
or ~0.19.0
. See npm's documentation about semver for more information.
This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.
Work around API deprecations in Deno 1.40.x (#3609, #3611)
Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.
Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop()
from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop()
function has been changed to return a promise, and you now have to change esbuild.stop()
to await esbuild.stop()
in all of your Deno tests.
Reorder implicit file extensions within node_modules
(#3341, #3608)
In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules
directories (i.e. in published packages) to prefer .js
over .ts
even when the --resolve-extensions=
order prefers .ts
over .js
(which it does by default). However, doing that also accidentally made esbuild prefer .css
over .ts
, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.
With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json
which used to become .jsx,.js,.css,.json,.tsx,.ts
in node_modules
directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json
instead.
Why even rewrite the implicit file extension order at all? One reason is because the .js
file is more likely to behave correctly than the .ts
file. The behavior of the .ts
file may depend on tsconfig.json
and the tsconfig.json
file may not even be published, or may use extends
to refer to a base tsconfig.json
file that wasn't published. People can get into this situation when they forget to add all .ts
files to their .npmignore
file before publishing to npm. Picking .js
over .ts
helps make it more likely that resulting bundle will behave correctly.
FAQs
The OpenBSD 64-bit binary for esbuild, a JavaScript bundler.
The npm package @esbuild/openbsd-x64 receives a total of 4,451,727 weekly downloads. As such, @esbuild/openbsd-x64 popularity was classified as popular.
We found that @esbuild/openbsd-x64 demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
We're introducing a new Analytics feature in the Socket dashboard so you can view changes in your organization's and repositories' alerts over time.
Security News
A new OpenSSF report uncovers critical gaps in secure software training, with 75% of new developers unfamiliar with secure practices, highlighting urgent educational needs.
Security News
The 2023 Python Developers Survey reveals key trends in packaging, web frameworks, and developer demographics, highlighting a shift toward innovative tools as the Python community diversifies and grows among less experienced developers.