chore(deps): update all non-major dependencies

Open renovate[bot] opened this issue 2 years ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
defu	`^6.0.0` -> `^6.0.1`
esbuild	`^0.14.47` -> `^0.15.3`
fs-extra	`^10.0.0` -> `^10.1.0`
globby	`^11.0.3` -> `^11.1.0`
jiti	`^1.12.9` -> `^1.14.0`
pathe	`^0.2.0` -> `^0.3.4`
pnpm (source)	`7.3.0` -> `7.9.0`

Release Notes

unjs/defu

`v0.15.3`

Compare Source

Change the Yarn PnP manifest to a singleton (#2463)

Previously esbuild searched for the Yarn PnP manifest in the parent directories of each file. But with Yarn's enableGlobalCache setting it's possible to configure Yarn PnP's implementation to reach outside of the directory subtree containing the Yarn PnP manifest. This was causing esbuild to fail to bundle projects with the enableGlobalCache setting enabled.

To handle this case, esbuild will now only search for the Yarn PnP manifest in the current working directory of the esbuild process. If you're using esbuild's CLI, this means you will now have to cd into the appropriate directory first. If you're using esbuild's API, you can override esbuild's value for the current working directory with the absWorkingDir API option.
Fix Yarn PnP resolution failures due to backslashes in paths on Windows (#2462)

Previously dependencies of a Yarn PnP virtual dependency failed to resolve on Windows. This was because Windows uses \ instead of / as a path separator, and the path manipulation algorithms used for Yarn PnP expected /. This release converts \ into / in Windows paths, which fixes this issue.
Fix sideEffects patterns containing slashes on Windows (#2465)

The sideEffects field in package.json lets you specify an array of patterns to mark which files have side effects (which causes all other files to be considered to not have side effects by exclusion). That looks like this:
```
"sideEffects": [
  "**/index.js",
  "**/index.prod.js"
]
```
However, the presence of the / character in the pattern meant that the pattern failed to match Windows-style paths, which broke sideEffects on Windows in this case. This release fixes this problem by adding additional code to handle Windows-style paths.

`v0.15.2`

Compare Source

Fix Yarn PnP issue with packages containing index.js (#2455, #2461)

Yarn PnP's tests require the resolved paths to end in /. That's not how the rest of esbuild's internals work, however, and doing this messed up esbuild's node module path resolution regarding automatically-detected index.js files. Previously packages that relied on implicit index.js resolution rules didn't work with esbuild under Yarn PnP. Removing this slash has fixed esbuild's path resolution behavior regarding index.js, which should now the same both with and without Yarn PnP.
Fix Yarn PnP support for extends in tsconfig.json (#2456)

Previously using extends in tsconfig.json with a path in a Yarn PnP package didn't work. This is because the process of setting up package path resolution rules requires parsing tsconfig.json files (due to the baseUrl and paths features) and resolving extends to a package path requires package path resolution rules to already be set up, which is a circular dependency. This cycle is broken by using special rules for extends in tsconfig.json that bypasses esbuild's normal package path resolution process. This is why using extends with a Yarn PnP package didn't automatically work. With this release, these special rules have been modified to check for a Yarn PnP manifest so this case should work now.
Fix Yarn PnP support in esbuild-wasm (#2458)

When running esbuild via WebAssembly, Yarn PnP support previously failed because Go's file system internals return EINVAL when trying to read a .zip file as a directory when run with WebAssembly. This was unexpected because Go's file system internals return ENOTDIR for this case on native. This release updates esbuild to treat EINVAL like ENOTDIR in this case, which fixes using esbuild-wasm to bundle a Yarn PnP project.

Note that to be able to use esbuild-wasm for Yarn PnP successfully, you currently have to run it using node instead of yarn node. This is because the file system shim that Yarn overwrites node's native file system API with currently generates invalid file descriptors with negative values when inside a .zip file. This prevents esbuild from working correctly because Go's file system internals don't expect syscalls that succeed without an error to return an invalid file descriptor. Yarn is working on fixing their use of invalid file descriptors.

`v0.15.1`

Compare Source

Update esbuild's Yarn Plug'n'Play implementation to match the latest specification changes (#2452, #2453)

This release updates esbuild's implementation of Yarn Plug'n'Play to match some changes to Yarn's specification that just landed. The changes are as follows:
- Check for platform-specific absolute paths instead of always for the / prefix
  
  The specification previously said that Yarn Plug'n'Play path resolution rules should not apply for paths that start with /. The intent was to avoid accidentally processing absolute paths. However, absolute paths on Windows such as C:\project start with drive letters instead of with /. So the specification was changed to instead explicitly avoid processing absolute paths.
- Make $$virtual an alias for __virtual__
  
  Supporting Yarn-style path resolution requires implementing a custom Yarn-specific path traversal scheme where certain path segments are considered no-ops. Specifically any path containing segments of the form __virtual__/<whatever>/<n> where <n> is an integer must be treated as if they were n times the .. operator instead (the <whatever> path segment is ignored). So /path/to/project/__virtual__/xyz/2/foo.js maps to the underlying file /path/to/project/../../foo.js. This scheme makes it possible for Yarn to get node (and esbuild) to load the same file multiple times (which is sometimes required for correctness) without actually duplicating the file on the file system.
  
  However, old versions of Yarn used to use $$virtual instead of __virtual__. This was changed because $$virtual was error-prone due to the use of the $ character, which can cause bugs when it's not correctly escaped within regular expressions. Now that esbuild makes $$virtual an alias for __virtual__, esbuild should now work with manifests from these old Yarn versions.
- Ignore PnP manifests in virtual directories
  
  The specification describes the algorithm for how to find the Plug'n'Play manifest when starting from a certain point in the file system: search through all parent directories in reverse order until the manifest is found. However, this interacts poorly with virtual paths since it can end up finding a virtual copy of the manifest instead of the original. To avoid this, esbuild now ignores manifests in virtual directories so that the search for the manifest will continue and find the original manifest in another parent directory later on.
These fixes mean that esbuild's implementation of Plug'n'Play now matches Yarn's implementation more closely, and esbuild can now correctly build more projects that use Plug'n'Play.

This release contains backwards-incompatible changes. Since esbuild is before version 1.0.0, these changes have been released as a new minor version to reflect this (as recommended by npm). You should either be pinning the exact version of esbuild in your package.json file or be using a version range syntax that only accepts patch upgrades such as ~0.14.0. See the documentation about semver for more information.

Implement the Yarn Plug'n'Play module resolution algorithm (#154, #237, #1263, #2451)

Node comes with a package manager called npm, which installs packages into a node_modules folder. Node and esbuild both come with built-in rules for resolving import paths to packages within node_modules, so packages installed via npm work automatically without any configuration. However, many people use an alternative package manager called Yarn. While Yarn can install packages using node_modules, it also offers a different package installation strategy called Plug'n'Play, which is often shortened to "PnP" (not to be confused with pnpm, which is an entirely different unrelated package manager).

Plug'n'Play installs packages as .zip files on your file system. The packages are never actually unzipped. Since Node doesn't know anything about Yarn's package installation strategy, this means you can no longer run your code with Node as it won't be able to find your packages. Instead, you need to run your code with Yarn, which applies patches to Node's file system APIs before running your code. These patches attempt to make zip files seem like normal directories. When running under Yarn, using Node's file system API to read ./some.zip/lib/file.js actually automatically extracts lib/file.js from ./some.zip at run-time as if it was a normal file. Other file system APIs behave similarly. However, these patches don't work with esbuild because esbuild is not written in JavaScript; it's a native binary executable that interacts with the file system directly through the operating system.

Previously the workaround for using esbuild with Plug'n'Play was to use the @yarnpkg/esbuild-plugin-pnp plugin with esbuild's JavaScript API. However, this wasn't great because the plugin needed to potentially intercept every single import path and file load to check whether it was a Plug'n'Play package, which has an unusually high performance cost. It also meant that certain subtleties of path resolution rules within a .zip file could differ slightly from the way esbuild normally works since path resolution inside .zip files was implemented by Yarn, not by esbuild (which is due to a limitation of esbuild's plugin API).

With this release, esbuild now contains an independent implementation of Yarn's Plug'n'Play algorithm (which is used when esbuild finds a .pnp.js, .pnp.cjs, or .pnp.data.json file in the directory tree). Creating additional implementations of this algorithm recently became possible because Yarn's package manifest format was recently documented: https://yarnpkg.com/advanced/pnp-spec/. This should mean that you can now use esbuild to bundle Plug'n'Play projects without any additional configuration (so you shouldn't need @yarnpkg/esbuild-plugin-pnp anymore). Bundling these projects should now happen much faster as Yarn no longer even needs to be run at all. Bundling the Yarn codebase itself with esbuild before and after this change seems to demonstrate over a 10x speedup (3.4s to 0.24s). And path resolution rules within Yarn packages should now be consistent with how esbuild handles regular Node packages. For example, fields such as module and browser in package.json files within .zip files should now be respected.

Keep in mind that this is brand new code and there may be some initial issues to work through before esbuild's implementation is solid. Yarn's Plug'n'Play specification is also brand new and may need some follow-up edits to guide new implementations to match Yarn's exact behavior. If you try this out, make sure to test it before committing to using it, and let me know if anything isn't working as expected. Should you need to debug esbuild's path resolution, you may find --log-level=verbose helpful.

`v0.14.54`

Compare Source

Fix optimizations for calls containing spread arguments (#2445)

This release fixes the handling of spread arguments in the optimization of /* @__PURE__ */ comments, empty functions, and identity functions:
```
// Original code
function empty() {}
function identity(x) { return x }
/* @&#8203;__PURE__ */ a(...x)
/* @&#8203;__PURE__ */ new b(...x)
empty(...x)
identity(...x)

// Old output (with --minify --tree-shaking=true)
...x;...x;...x;...x;

// New output (with --minify --tree-shaking=true)
function identity(n){return n}[...x];[...x];[...x];identity(...x);
```
Previously esbuild assumed arguments with side effects could be directly inlined. This is almost always true except for spread arguments, which are not syntactically valid on their own and which have the side effect of causing iteration, which might have further side effects. Now esbuild will wrap these elements in an unused array so that they are syntactically valid and so that the iteration side effects are preserved.

`v0.14.53`

Compare Source

This release fixes a minor issue with the previous release: I had to rename the package esbuild-linux-loong64 to @esbuild/linux-loong64 in the contributed PR because someone registered the package name before I could claim it, and I missed a spot. Hopefully everything is working after this release. I plan to change all platform-specific package names to use the @esbuild/ scope at some point to avoid this problem in the future.

`v0.14.52`

Compare Source

Allow binary data as input to the JS transform and build APIs (#2424)

Previously esbuild's transform and build APIs could only take a string. However, some people want to use esbuild to convert binary data to base64 text. This is problematic because JavaScript strings represent UTF-16 text and esbuild internally operates on arrays of bytes, so all strings coming from JavaScript undergo UTF-16 to UTF-8 conversion before use. This meant that using esbuild in this way was doing base64 encoding of the UTF-8 encoding of the text, which was undesired.

With this release, esbuild now accepts Uint8Array in addition to string as an input format for the transform and build APIs. Now you can use esbuild to convert binary data to base64 text:

// Original code
import esbuild from 'esbuild'
console.log([
  (await esbuild.transform('\xFF', { loader: 'base64' })).code,
  (await esbuild.build({ stdin: { contents: '\xFF', loader: 'base64' }, write: false })).outputFiles[0].text,
])
console.log([
  (await esbuild.transform(new Uint8Array([0xFF]), { loader: 'base64' })).code,
  (await esbuild.build({ stdin: { contents: new Uint8Array([0xFF]), loader: 'base64' }, write: false })).outputFiles[0].text,
])

// Old output
[ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
/* ERROR: The input to "transform" must be a string */

// New output
[ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
[ 'module.exports = "/w==";\n', 'module.exports = "/w==";\n' ]

Update the getter for text in build results (#2423)

Output files in build results returned from esbuild's JavaScript API have both a contents and a text property to return the contents of the output file. The contents property is a binary UTF-8 Uint8Array and the text property is a JavaScript UTF-16 string. The text property is a getter that does the UTF-8 to UTF-16 conversion only if it's needed for better performance.

Previously if you mutate the build results object, you had to overwrite both contents and text since the value returned from the text getter is the original text returned by esbuild. Some people find this confusing so with this release, the getter for text has been updated to do the UTF-8 to UTF-16 conversion on the current value of the contents property instead of the original value.
Publish builds for Linux LoongArch 64-bit (#1804, #2373)

This release upgrades to Go 1.19, which now includes support for LoongArch 64-bit processors. LoongArch 64-bit builds of esbuild will now be published to npm, which means that in theory they can now be installed with npm install esbuild. This was contributed by @beyond-1234.

`v0.14.51`

Compare Source

Add support for React 17's automatic JSX transform (#334, #718, #1172, #2318, #2349)

This adds support for the new "automatic" JSX runtime from React 17+ to esbuild for both the build and transform APIs.

New CLI flags and API options:
- --jsx, jsx — Set this to "automatic" to opt in to this new transform
- --jsx-dev, jsxDev — Toggles development mode for the automatic runtime
- --jsx-import-source, jsxImportSource — Overrides the root import for runtime functions (default "react")
New JSX pragma comments:
- @jsxRuntime — Sets the runtime (automatic or classic)
- @jsxImportSource — Sets the import source (only valid with automatic runtime)
The existing @jsxFragment and @jsxFactory pragma comments are only valid with "classic" runtime.

TSConfig resolving: Along with accepting the new options directly via CLI or API, option inference from tsconfig.json compiler options was also implemented:
- "jsx": "preserve" or "jsx": "react-native" → Same as --jsx=preserve in esbuild
- "jsx": "react" → Same as --jsx=transform in esbuild (which is the default behavior)
- "jsx": "react-jsx" → Same as --jsx=automatic in esbuild
- "jsx": "react-jsxdev" → Same as --jsx=automatic --jsx-dev in esbuild
It also reads the value of "jsxImportSource" from tsconfig.json if specified.

For react-jsx it's important to note that it doesn't implicitly disable --jsx-dev. This is to support the case where a user sets "react-jsx" in their tsconfig.json but then toggles development mode directly in esbuild.

esbuild vs Babel vs TS vs...

There are a few differences between the various technologies that implement automatic JSX runtimes. The JSX transform in esbuild follows a mix of Babel's and TypeScript's behavior:
- When an element has __source or __self props:
  - Babel: Print an error about a deprecated transform plugin
  - TypeScript: Allow the props
  - swc: Hard crash
  - esbuild: Print an error — Following Babel was chosen for this one because this might help people catch configuration issues where JSX files are being parsed by multiple tools
- Element has an "implicit true" key prop, e.g. <a key />:
  - Babel: Print an error indicating that "key" props require an explicit value
  - TypeScript: Silently omit the "key" prop
  - swc: Hard crash
  - esbuild: Print an error like Babel — This might help catch legitimate programming mistakes
- Element has spread children, e.g. <a>{...children}</a>
  - Babel: Print an error stating that React doesn't support spread children
  - TypeScript: Use static jsx function and pass children as-is, including spread operator
  - swc: same as Babel
  - esbuild: Same as TypeScript
Also note that TypeScript has some bugs regarding JSX development mode and the generation of lineNumber and columnNumber values. Babel's values are accurate though, so esbuild's line and column numbers match Babel. Both numbers are 1-based and columns are counted in terms of UTF-16 code units.

This feature was contributed by @jgoz.

`v0.14.50`

Compare Source

Emit names in source maps (#1296)

The source map specification includes an optional names field that can associate an identifier with a mapping entry. This can be used to record the original name for an identifier, which is useful if the identifier was renamed to something else in the generated code. When esbuild was originally written, this field wasn't widely used, but now there are some debuggers that make use of it to provide better debugging of minified code. With this release, esbuild now includes a names field in the source maps that it generates. To save space, the original name is only recorded when it's different from the final name.
Update parser for arrow functions with initial default type parameters in .tsx files (#2410)

TypeScript 4.6 introduced a change to the parsing of JSX syntax in .tsx files. Now a < token followed by an identifier and then a = token is parsed as an arrow function with a default type parameter instead of as a JSX element. This release updates esbuild's parser to match TypeScript's parser.
Fix an accidental infinite loop with --define substitution (#2407)

This is a fix for a regression that was introduced in esbuild version 0.14.44 where certain --define substitutions could result in esbuild crashing with a stack overflow. The problem was an incorrect fix for #2292. The fix merged the code paths for --define and --jsx-factory rewriting since the value substitution is now the same for both. However, doing this accidentally made --define substitution recursive since the JSX factory needs to be able to match against --define substitutions to integrate with the --inject feature. The fix is to only do one additional level of matching against define substitutions, and to only do this for JSX factories. Now these cases are able to build successfully without a stack overflow.
Include the "public path" value in hashes (#2403)

The --public-path= configuration value affects the paths that esbuild uses to reference files from other files and is used in various situations such as cross-chunk imports in JS and references to asset files from CSS files. However, it wasn't included in the hash calculations used for file names due to an oversight. This meant that changing the public path setting incorrectly didn't result in the hashes in file names changing even though the contents of the files changed. This release fixes the issue by including a hash of the public path in all non-asset output files.
Fix a cross-platform consistency bug (#2383)

Previously esbuild would minify 0xFFFF_FFFF_FFFF_FFFF as 0xffffffffffffffff (18 bytes) on arm64 chips and as 18446744073709552e3 (19 bytes) on x86_64 chips. The reason was that the number was converted to a 64-bit unsigned integer internally for printing as hexadecimal, the 64-bit floating-point number 0xFFFF_FFFF_FFFF_FFFF is actually 0x1_0000_0000_0000_0180 (i.e. it's rounded up, not down), and converting float64 to uint64 is implementation-dependent in Go when the input is out of bounds. This was fixed by changing the upper limit for which esbuild uses hexadecimal numbers during minification to 0xFFFF_FFFF_FFFF_F800, which is the next representable 64-bit floating-point number below 0x1_0000_0000_0000_0180, and which fits in a uint64. As a result, esbuild will now consistently never minify 0xFFFF_FFFF_FFFF_FFFF as 0xffffffffffffffff anymore, which means the output should now be consistent across platforms.
Fix a hang with the synchronous API when the package is corrupted (#2396)

An error message is already thrown when the esbuild package is corrupted and esbuild can't be run. However, if you are using a synchronous call in the JavaScript API in worker mode, esbuild will use a child worker to initialize esbuild once so that the overhead of initializing esbuild can be amortized across multiple synchronous API calls. However, errors thrown during initialization weren't being propagated correctly which resulted in a hang while the main thread waited forever for the child worker to finish initializing. With this release, initialization errors are now propagated correctly so calling a synchronous API call when the package is corrupted should now result in an error instead of a hang.
Fix tsconfig.json files that collide with directory names (#2411)

TypeScript lets you write tsconfig.json files with extends clauses that refer to another config file using an implicit .json file extension. However, if the config file without the .json extension existed as a directory name, esbuild and TypeScript had different behavior. TypeScript ignores the directory and continues looking for the config file by adding the .json extension while esbuild previously terminated the search and then failed to load the config file (because it's a directory). With this release, esbuild will now ignore exact matches when resolving extends fields in tsconfig.json files if the exact match results in a directory.
Add platform to the transform API (#2362)

The platform option is mainly relevant for bundling because it mostly affects path resolution (e.g. activating the "browser" field in package.json files), so it was previously only available for the build API. With this release, it has additionally be made available for the transform API for a single reason: you can now set --platform=node when transforming a string so that esbuild will add export annotations for node, which is only relevant when --format=cjs is also present.

This has to do with an implementation detail of node that parses the AST of CommonJS files to discover named exports when importing CommonJS from ESM. However, this new addition to esbuild's API is of questionable usefulness. Node's loader API (the main use case for using esbuild's transform API like this) actually bypasses the content returned from the loader and parses the AST that's present on the file system, so you won't actually be able to use esbuild's API for this. See the linked issue for more information.

`v0.14.49`

Compare Source

Keep inlined constants when direct eval is present (#2361)

Version 0.14.19 of esbuild added inlining of certain const variables during minification, which replaces all references to the variable with the initializer and then removes the variable declaration. However, this could generate incorrect code when direct eval is present because the direct eval could reference the constant by name. This release fixes the problem by preserving the const variable declaration in this case:
```
// Original code
console.log((() => { const x = 123; return x + eval('x') }))

// Old output (with --minify)
console.log(()=>123+eval("x"));

// New output (with --minify)
console.log(()=>{const x=123;return 123+eval("x")});
```
Fix an incorrect error in TypeScript when targeting ES5 (#2375)

Previously when compiling TypeScript code to ES5, esbuild could incorrectly consider the following syntax forms as a transformation error:
```
0 ? ([]) : 1 ? ({}) : 2;
```
The error messages looked like this:
```
✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet

    example.ts:1:5:
      1 │ 0 ? ([]) : 1 ? ({}) : 2;
        ╵      ^

✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet

    example.ts:1:16:
      1 │ 0 ? ([]) : 1 ? ({}) : 2;
        ╵                 ^
```
These parenthesized literals followed by a colon look like the start of an arrow function expression followed by a TypeScript return type (e.g. ([]) : 1 could be the start of the TypeScript arrow function ([]): 1 => 1). Unlike in JavaScript, parsing arrow functions in TypeScript requires backtracking. In this case esbuild correctly determined that this expression wasn't an arrow function after all but the check for destructuring was incorrectly not covered under the backtracking process. With this release, the error message is now only reported if the parser successfully parses an arrow function without backtracking.
Fix generated TypeScript enum comments containing */ (#2369, #2371)

TypeScript enum values that are equal to a number or string literal are inlined (references to the enum are replaced with the literal value) and have a /* ... */ comment after them with the original enum name to improve readability. However, this comment is omitted if the enum name contains the character sequence */ because that would end the comment early and cause a syntax error:
```
// Original TypeScript
enum Foo { '/*' = 1, '*/' = 2 }
console.log(Foo['/*'], Foo['*/'])

// Generated JavaScript
console.log(1 /* /* */, 2);
```
This was originally handled correctly when TypeScript enum inlining was initially implemented since it was only supported within a single file. However, when esbuild was later extended to support TypeScript enum inlining across files, this special case where the enum name contains */ was not handled in that new code. Starting with this release, esbuild will now handle enums with names containing */ correctly when they are inlined across files:
```
// foo.ts
export enum Foo { '/*' = 1, '*/' = 2 }

// bar.ts
import { Foo } from './foo'
console.log(Foo['/*'], Foo['*/'])

// Old output (with --bundle --format=esm)
console.log(1 /* /* */, 2 /* */ */);

// New output (with --bundle --format=esm)
console.log(1 /* /* */, 2);
```
This fix was contributed by @magic-akari.
Allow declare class fields to be initialized (#2380)

This release fixes an oversight in the TypeScript parser that disallowed initializers for declare class fields. TypeScript actually allows the following limited initializer expressions for readonly fields:
```
declare const enum a { b = 0 }

class Foo {
  // These are allowed by TypeScript
  declare readonly a = 0
  declare readonly b = -0
  declare readonly c = 0n
  declare readonly d = -0n
  declare readonly e = 'x'
  declare readonly f = `x`
  declare readonly g = a.b
  declare readonly h = a['b']

  // These are not allowed by TypeScript
  declare readonly x = (0)
  declare readonly y = null
  declare readonly z = -a.b
}
```
So with this release, esbuild now allows initializers for declare class fields too. To future-proof this in case TypeScript allows more expressions as initializers in the future (such as null), esbuild will allow any expression as an initializer and will leave the specifics of TypeScript's special-casing here to the TypeScript type checker.
Fix a bug in esbuild's feature compatibility table generator (#2365)

Passing specific JavaScript engines to esbuild's --target flag restricts esbuild to only using JavaScript features that are supported on those engines in the output files that esbuild generates. The data for this feature is automatically derived from this compatibility table with a script: https://kangax.github.io/compat-table/.

However, the script had a bug that could incorrectly consider a JavaScript syntax feature to be supported in a given engine even when it doesn't actually work in that engine. Specifically this bug happened when a certain aspect of JavaScript syntax has always worked incorrectly in that engine and the bug in that engine has never been fixed. This situation hasn't really come up before because previously esbuild pretty much only targeted JavaScript engines that always fix their bugs, but the two new JavaScript engines that were added in the previous release (Hermes and Rhino) have many aspects of the JavaScript specification that have never been implemented, and may never be implemented. For example, the let and const keywords are not implemented correctly in those engines.

With this release, esbuild's compatibility table generator script has been fixed and as a result, esbuild will now correctly consider a JavaScript syntax feature to be unsupported in a given engine if there is some aspect of that syntax that is broken in all known versions of that engine. This means that the following JavaScript syntax features are no longer considered to be supported by these engines (represented using esbuild's internal names for these syntax features):

Hermes:
- arrow
- const-and-let
- default-argument
- generator
- optional-catch-binding
- optional-chain
- rest-argument
- template-literal
Rhino:
- arrow
- const-and-let
- destructuring
- for-of
- generator
- object-extensions
- template-literal
IE:
- const-and-let

`v0.14.48`

Compare Source

Enable using esbuild in Deno via WebAssembly (#2323)

The native implementation of esbuild is much faster than the WebAssembly version, but some people don't want to give Deno the --allow-run permission necessary to run esbuild and are ok waiting longer for their builds to finish when using the WebAssembly backend. With this release, you can now use esbuild via WebAssembly in Deno. To do this you will need to import from wasm.js instead of mod.js:
```
import * as esbuild from 'https://deno.land/x/[email protected]/wasm.js'
const ts = 'let test: boolean = true'
const result = await esbuild.transform(ts, { loader: 'ts' })
console.log('result:', result)
```
Make sure you run Deno with --allow-net so esbuild can download the WebAssembly module. Using esbuild like this starts up a worker thread that runs esbuild in parallel (unless you call esbuild.initialize({ worker: false }) to tell esbuild to run on the main thread). If you want to, you can call esbuild.stop() to terminate the worker if you won't be using esbuild anymore and you want to reclaim the memory.

Note that Deno appears to have a bug where background WebAssembly optimization can prevent the process from exiting for many seconds. If you are trying to use Deno and WebAssembly to run esbuild quickly, you may need to manually call Deno.exit(0) after your code has finished running.
Add support for font file MIME types (#2337)

This release adds support for font file MIME types to esbuild, which means they are now recognized by the built-in local web server and they are now used when a font file is loaded using the dataurl loader. The full set of newly-added file extension MIME type mappings is as follows:
- .eot => application/vnd.ms-fontobject
- .otf => font/otf
- .sfnt => font/sfnt
- .ttf => font/ttf
- .woff => font/woff
- .woff2 => font/woff2
Remove "use strict"; when targeting ESM (#2347)

All ES module code is automatically in strict mode, so a "use strict"; directive is unnecessary. With this release, esbuild will now remove the "use strict"; directive if the output format is ESM. This change makes the generated output file a few bytes smaller:
```
// Original code
'use strict'
export let foo = 123

// Old output (with --format=esm --minify)
"use strict";let t=123;export{t as foo};

// New output (with --format=esm --minify)
let t=123;export{t as foo};
```
Attempt to have esbuild work with Deno on FreeBSD (#2356)

Deno doesn't support FreeBSD, but it's possible to build Deno for FreeBSD with some additional patches on top. This release of esbuild changes esbuild's Deno installer to download esbuild's FreeBSD binary in this situation. This configuration is unsupported although in theory everything should work.
Add some more target JavaScript engines (#2357)

This release adds the Rhino and Hermes JavaScript engines to the set of engine identifiers that can be passed to the --target flag. You can use this to restrict esbuild to only using JavaScript features that are supported on those engines in the output files that esbuild generates.

jprichardson/node-fs-extra

`v10.1.0`

Compare Source

Warn if fs.realpath.native does not exist, instead of erroring (#953)
Allow explicitly passing undefined options to move() (#947, #955)
Use process.emitWarning instead of console.warn (#954)

`v10.0.1`

Compare Source

Add sideEffects: false to package.json (#941)

sindresorhus/globby

`v11.1.0`

Compare Source

Update dependencies to fix some npm audit notices

`v11.0.4`

Compare Source

Support objectMode option in the TypeScript types (#178) a08264f

unjs/jiti

`v1.14.0`

Compare Source

Features

detect native esm using type: module (#67) (986f146)

Bug Fixes

use inlined import meta plugin to inject url (#68) (b52bb17)

`v1.13.0`

Compare Source

Features

support inline sourceMaps for easier debugging (#46) (888db00)

Bug Fixes

use backslash to make import maps working in windows (e8696c7)

1.12.15 (2022-01-28)

Bug Fixes

force transpile config package (2ddcb8a), closes #56

1.12.14 (2022-01-26)

Bug Fixes

move esm resolve behind a flag (60e094c)

1.12.13 (2022-01-25)

1.12.12 (2022-01-25)

Bug Fixes

ensure resolve esm id exists (2d44274)

1.12.11 (2022-01-25)

Bug Fixes

default _filename if null or falsy value passed (1a24f2a)
pkg: do not mangle dist build (3b456e1)

1.12.10 (2022-01-25)

Bug Fixes

support resolving with import condition (#52) (1e1bb0c)

1.12.9 (2021-10-18)

Bug Fixes

inline mlly.interopDefault (resolves #48) (32e606f)

1.12.8 (2021-10-18)

Bug Fixes

update mlly to latest (cf178ce)

1.12.7 (2021-10-12)

1.12.6 (2021-10-02)

Bug Fixes

avoid detecting dynamic import as esm syntax (0b904a9)

1.12.5 (2021-09-29)

Bug Fixes

remove dynamicImport from options (ad42dd1)

1.12.4 (2021-09-29)

Bug Fixes

remove v8-compile-cache integration (a9fe3a0)

1.12.3 (2021-09-21)

Bug Fixes

interopDefault: allow recursive default (55e0f62)

1.12.2 (2021-09-21)

Bug Fixes

interopDefault: handle cjs cache (1f3e4c3)

1.12.1 (2021-09-21)

Bug Fixes

interopDefault: support mixed CJS + default (4392c6a)

⚠ BREAKING CHANGES

import pathe from 'pathe should be changes to import * as pathe from 'pathe'
implement rest of path minimally (#10)

Features

implement rest of path minimally (#10) (6136b3c)

Bug Fixes

avoid mixed named and default exports (89e35ad)

pnpm/pnpm

`v7.9.0`

Compare Source

Minor Changes

When ignore-dep-scripts is true, ignore scripts of dependencies but run the scripts of the project.
When ignore-compatibility-db is set to true, the compatibility database will not be used to patch dependencies #5132.
Print the versions of packages in peer dependency warnings and errors.
Support a new hook for passing a custom package importer to the store controller.

Patch Changes

Don't print the same deprecation warning multiple times.
On POSIX pnpm setup should suggest users to source the config instead of restarting the terminal.
Installing a package with bin that points to an .exe file on Windows #5159.
Fix bug where the package manifest was not resolved if verify-store-integrity is set to false.
Fix sorting of keys in lockfile to make it more deterministic and prevent unnecessary churn in the lockfile #5151.
Don't create a separate bundle for pnpx.

Our Gold Sponsors

#### Our Silver Sponsors

`v7.8.0`

Compare Source

Minor Changes

When publishConfig.directory is set, only symlink it to other workspace projects if publishConfig.linkDirectory is set to true. Otherwise, only use it for publishing #5115.

Patch Changes

Don't incorrectly identify a lockfile out-of-date when the package has a publishConfig.directory field #5124.
Don't crash when a config file contains a setting w

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

Jun 23 '22 18:06 renovate[bot]

Codecov Report

Merging #43 (1c0b6c0) into main (bcff149) will increase coverage by 75.23%. The diff coverage is n/a.

:exclamation: Current head 1c0b6c0 differs from pull request most recent head 01a8a1c. Consider uploading reports for the commit 01a8a1c to get more accurate results

@@            Coverage Diff            @@
##           main      #43       +/-   ##
=========================================
+ Coverage      0   75.23%   +75.23%     
=========================================
  Files         0        6        +6     
  Lines         0      323      +323     
  Branches      0       70       +70     
=========================================
+ Hits          0      243      +243     
- Misses        0       15       +15     
- Partials      0       65       +65

Impacted Files	Coverage Δ
src/loader.ts	`90.41% <0.00%> (ø)`
src/loaders/js.ts	`70.00% <0.00%> (ø)`
src/loaders/vue.ts	`70.45% <0.00%> (ø)`
src/make.ts	`68.90% <0.00%> (ø)`
src/utils/dts.ts	`77.14% <0.00%> (ø)`
src/loaders/index.ts	`100.00% <0.00%> (ø)`

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Jul 22 '22 13:07 codecov[bot]

mkdist mkdist copied to clipboard

chore(deps): update all non-major dependencies

Release Notes

Features

Bug Fixes

Features

Bug Fixes

1.12.15 (2022-01-28)

Bug Fixes

1.12.14 (2022-01-26)

Bug Fixes

1.12.13 (2022-01-25)

1.12.12 (2022-01-25)

Bug Fixes

1.12.11 (2022-01-25)

Bug Fixes

1.12.10 (2022-01-25)

Bug Fixes

1.12.9 (2021-10-18)

Bug Fixes

1.12.8 (2021-10-18)

Bug Fixes

1.12.7 (2021-10-12)

1.12.6 (2021-10-02)

Bug Fixes

1.12.5 (2021-09-29)

Bug Fixes

1.12.4 (2021-09-29)

Bug Fixes

1.12.3 (2021-09-21)

Bug Fixes

1.12.2 (2021-09-21)

Bug Fixes

1.12.1 (2021-09-21)

Bug Fixes

⚠ BREAKING CHANGES

Features

Bug Fixes

Minor Changes

Patch Changes

Our Gold Sponsors

Minor Changes

Patch Changes

Configuration

Codecov Report

mkdist
mkdist copied to clipboard