v1.9.0

Compare Source

What's Changed

• fix data race and use-after-free in napi_threadsafe_function by @​toyobayashi in #​199
  • fix tsfn not work in JS based async_work workers
  • fix pthread_create not work in JS based async_work workers
  • emnapi_basic[-mt].a includes libuv symbols now
• refactor: dispatch async work queue in shared memory by @​toyobayashi in #​200
  • Avoids deadlock when main thread block on waiting queued async work starting. Completed work can not be dispatched to main thread that cause no new worker available, then queued work never start.
  • wasm32-wasip1-threads target spawn async worker in JS will use pthread_create, no longer maintain a separate worker pool.
• rename node_api_create_object_with_properties by @​toyobayashi in #​193
• fix: execute tsfn finalizer after queue drains when aborted
• feat: add required config hint in package entry

  const { requiredConfig } = require('emnapi')
  console.log(requiredConfig.clang.wasmld)

  [
    '--import-memory',
    '--shared-memory',
    '--export-table',
    '--export=malloc',
    '--export=free',
    '--export=napi_register_wasm_v1',
    '--export-if-defined=node_api_module_get_api_version_v1',
    '--export=emnapi_thread_crashed',
    '--export-if-defined=emnapi_async_worker_create',
    '--export-if-defined=emnapi_async_worker_init'
  ]
  

Full Changelog: toyobayashi/emnapi@v1.8.1...v1.9.0

v0.27.4

Compare Source

• Fix a regression with CSS media queries (#​4395, #​4405, #​4406)

  Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the <media-type> and <media-condition-without-or> grammar. Specifically, esbuild was failing to wrap an or clause with parentheses when inside <media-condition-without-or>. This release fixes the regression.

  Here is an example:

  /* Original code */
  @​media only screen and ((min-width: 10px) or (min-height: 10px)) {
    a { color: red }
  }
  
  /* Old output (incorrect) */
  @​media only screen and (min-width: 10px) or (min-height: 10px) {
    a {
      color: red;
    }
  }
  
  /* New output (correct) */
  @​media only screen and ((min-width: 10px) or (min-height: 10px)) {
    a {
      color: red;
    }
  }

• Fix an edge case with the inject feature (#​4407)

  This release fixes an edge case where esbuild's inject feature could not be used with arbitrary module namespace names exported using an export {} from statement with bundling disabled and a target environment where arbitrary module namespace names is unsupported.

  With the fix, the following inject file:

  import jquery from 'jquery';
  export { jquery as 'window.jQuery' };

  Can now always be rewritten as this without esbuild sometimes incorrectly generating an error:

  export { default as 'window.jQuery' } from 'jquery';

• Attempt to improve API handling of huge metafiles (#​4329, #​4415)

  This release contains a few changes that attempt to improve the behavior of esbuild's JavaScript API with huge metafiles (esbuild's name for the build metadata, formatted as a JSON object). The JavaScript API is designed to return the metafile JSON as a JavaScript object in memory, which makes it easy to access from within a JavaScript-based plugin. Multiple people have encountered issues where this API breaks down with a pathologically-large metafile.

  The primary issue is that V8 has an implementation-specific maximum string length, so using the JSON.parse API with large enough strings is impossible. This release will now attempt to use a fallback JavaScript-based JSON parser that operates directly on the UTF8-encoded JSON bytes instead of using JSON.parse when the JSON metafile is too big to fit in a JavaScript string. The new fallback path has not yet been heavily-tested. The metafile will also now be generated with whitespace removed if the bundle is significantly large, which will reduce the size of the metafile JSON slightly.

  However, hitting this case is potentially a sign that something else is wrong. Ideally you wouldn't be building something so enormous that the build metadata can't even fit inside a JavaScript string. You may want to consider optimizing your project, or breaking up your project into multiple parts that are built independently. Another option could potentially be to use esbuild's command-line API instead of its JavaScript API, which is more efficient (although of course then you can't use JavaScript plugins, so it may not be an option).

v9.0.6

Compare Source

Bug Fixes

• deps: add missing ci-info dependency (#​4263) (b768187)
• deps: bump tar from 7.5.8 to 7.5.11 (#​4296) (7a69a57)

v16.3.3

Compare Source

Patch Changes

• #​1740 0109e8d Thanks @​iiroj! - Make sure Git's warning about CRLF line-endings doesn't interfere with creating initial backup stash.

v3.33.0

Compare Source

Minor Changes

• a263635: Use pathspec wrappers for remote and local paths when running either git.clone or git.mirror to
  avoid leaving them less open for unexpected outcomes when passing unsanitised data into these tasks.

Patch Changes

• e253a0d: Enhanced git -c checks in unsafe plugin.

  Thanks to @​JohannesLks for identifying the issue