visulima / packem

A fast and modern bundler for Node.js and TypeScript.
MIT License
3 stars 0 forks source link

fix(deps): update minor updates (minor) #33

Open renovate[bot] opened 1 week ago

renovate[bot] commented 1 week ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ckeditor/typedoc-plugins (source) 44.0.0 -> 44.1.1 age adoption passing confidence
esbuild ^0.20.2 \|\| ^0.21.3 -> ^0.20.2 \|\| ^0.21.3 \|\| ^0.24.0 age adoption passing confidence
oxc-parser (source) 0.30.5 -> 0.31.0 age adoption passing confidence
oxc-transform (source) ^0.20.0 -> ^0.31.0 age adoption passing confidence
oxc-transform (source) ^0.30.5 -> ^0.31.0 age adoption passing confidence

Release Notes

ckeditor/ckeditor5-dev (@​ckeditor/typedoc-plugins) ### [`v44.1.1`](https://redirect.github.com/ckeditor/ckeditor5-dev/releases/tag/v44.1.1): (next) [Compare Source](https://redirect.github.com/ckeditor/ckeditor5-dev/compare/v44.1.0...v44.1.1) > \[!NOTE] > The release channel for this release is `next`. ##### Bug fixes - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: Added a missing dependency (simple-git). ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/914436ff2d14b8e44a767a8c66a3d36fe832158b)) ##### Released packages Check out the [Versioning policy](https://ckeditor.com/docs/ckeditor5/latest/framework/guides/support/versioning-policy.html) guide for more information.
Released packages (summary) Other releases: - [@​ckeditor/ckeditor5-dev-build-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-build-tools/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-bump-year](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-bump-year/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-ci](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-ci/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-dependency-checker](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-dependency-checker/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-docs](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-docs/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-stale-bot](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-stale-bot/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-tests](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-tests/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-transifex](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-transifex/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-translations](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-translations/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-utils](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-utils/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/ckeditor5-dev-web-crawler](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-web-crawler/v/44.1.1): v44.1.0 => v44.1.1 - [@​ckeditor/typedoc-plugins](https://www.npmjs.com/package/@​ckeditor/typedoc-plugins/v/44.1.1): v44.1.0 => v44.1.1
### [`v44.1.0`](https://redirect.github.com/ckeditor/ckeditor5-dev/releases/tag/v44.1.0): (next) [Compare Source](https://redirect.github.com/ckeditor/ckeditor5-dev/compare/v44.0.0...v44.1.0) > \[!NOTE] > The release channel for this release is `next`. ##### Features - **[ci](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-ci)**: Created a new binary script called `ckeditor5-dev-ci-is-workflow-restarted` that returns with a non-zero exit code if a given workflow is executed for the first time. The restarted workflows exit with a zero exit code. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/ff7d7387cc46fc24d7992178f331f29df50f7e53)) - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: A user-provided version will be checked against npm availability while generating a changelog. If it is already taken, the tools will not allow it to be used. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/ff7d7387cc46fc24d7992178f331f29df50f7e53)) ##### Other changes - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: The `updateVersions()` task will no longer verify if the specified `version` is available on npm. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/ff7d7387cc46fc24d7992178f331f29df50f7e53)) - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: The `publishPackages()` task filters out already published packages to avoid pushing the same archive twice. Thanks to that, it can be a part of a process that would be restarted. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/ff7d7387cc46fc24d7992178f331f29df50f7e53)) - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: The `publishPackages()` task tries to publish the package once again when it fails independently of the returned error code. Previously, it was scheduled only when the `E409` error occurred. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/ff7d7387cc46fc24d7992178f331f29df50f7e53)) - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: Marked the `verifyPackagesPublishedCorrectly()` function is deprecated. Its responsibility has been merged with `publishPackages()`. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/ff7d7387cc46fc24d7992178f331f29df50f7e53)) - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: The `commitAndTag()` task does not commit files if a tag for the specified version is already created. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/ff7d7387cc46fc24d7992178f331f29df50f7e53)) - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: We do not spawn an npm process to download a package manifest from the npm registry. Instead, we send an HTTP request using the `pacote` package. Closes [ckeditor/ckeditor5#17191](https://redirect.github.com/ckeditor/ckeditor5/issues/17191). ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/a155390a2ee45190ce6edc49ed48f8e871aa641f)) - **[release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools)**: The `getNpmTagFromVersion()` function returns a `'nightly'` string when passing a CKEditor 5 nightly version. ([commit](https://redirect.github.com/ckeditor/ckeditor5-dev/commit/4edf71cade5c73a8f9a7dbf80994490eeb400b60)) ##### Released packages Check out the [Versioning policy](https://ckeditor.com/docs/ckeditor5/latest/framework/guides/support/versioning-policy.html) guide for more information.
Released packages (summary) Releases containing new features: - [@​ckeditor/ckeditor5-dev-ci](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-ci/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-release-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-release-tools/v/44.1.0): v44.0.0 => v44.1.0 Other releases: - [@​ckeditor/ckeditor5-dev-build-tools](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-build-tools/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-bump-year](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-bump-year/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-dependency-checker](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-dependency-checker/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-docs](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-docs/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-stale-bot](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-stale-bot/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-tests](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-tests/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-transifex](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-transifex/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-translations](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-translations/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-utils](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-utils/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/ckeditor5-dev-web-crawler](https://www.npmjs.com/package/@​ckeditor/ckeditor5-dev-web-crawler/v/44.1.0): v44.0.0 => v44.1.0 - [@​ckeditor/typedoc-plugins](https://www.npmjs.com/package/@​ckeditor/typedoc-plugins/v/44.1.0): v44.0.0 => v44.1.0
evanw/esbuild (esbuild) ### [`v0.24.0`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0240) [Compare Source](https://redirect.github.com/evanw/esbuild/compare/v0.23.1...v0.24.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.23.0` or `~0.23.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. - Drop support for older platforms ([#​3902](https://redirect.github.com/evanw/esbuild/pull/3902)) This release drops support for the following operating system: - macOS 10.15 Catalina This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later. Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this: git clone https://github.com/evanw/esbuild.git cd esbuild go build ./cmd/esbuild ./esbuild --version - Fix class field decorators in TypeScript if `useDefineForClassFields` is `false` ([#​3913](https://redirect.github.com/evanw/esbuild/issues/3913)) Setting the `useDefineForClassFields` flag to `false` in `tsconfig.json` means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release. - Avoid incorrect cycle warning with `tsconfig.json` multiple inheritance ([#​3898](https://redirect.github.com/evanw/esbuild/issues/3898)) TypeScript 5.0 introduced multiple inheritance for `tsconfig.json` files where `extends` can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, `tsconfig.json` files containing this edge case should work correctly without generating a warning. - Handle Yarn Plug'n'Play stack overflow with `tsconfig.json` ([#​3915](https://redirect.github.com/evanw/esbuild/issues/3915)) Previously a `tsconfig.json` file that `extends` another file in a package with an `exports` map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release. - Work around more issues with Deno 1.31+ ([#​3917](https://redirect.github.com/evanw/esbuild/pull/3917)) This version of Deno broke the `stdin` and `stdout` properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when `import.meta.main` is `true`). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release. This fix was contributed by [@​Joshix-1](https://redirect.github.com/Joshix-1). ### [`v0.23.1`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0231) [Compare Source](https://redirect.github.com/evanw/esbuild/compare/v0.23.0...v0.23.1) - Allow using the `node:` import prefix with `es*` targets ([#​3821](https://redirect.github.com/evanw/esbuild/issues/3821)) The [`node:` prefix on imports](https://nodejs.org/api/esm.html#node-imports) is an alternate way to import built-in node modules. For example, `import fs from "fs"` can also be written `import fs from "node:fs"`. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with `--target=node14` so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as `--target=node18,es2022` removes the `node:` prefix because none of the `es*` targets are known to support this feature. This release adds the support for the `node:` flag to esbuild's internal compatibility table for `es*` to allow you to use compound targets like this: ```js // Original code import fs from 'node:fs' fs.open // Old output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "fs"; fs.open; // New output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "node:fs"; fs.open; ``` - Fix a panic when using the CLI with invalid build flags if `--analyze` is present ([#​3834](https://redirect.github.com/evanw/esbuild/issues/3834)) Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the `--analyze` flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how `--analyze` is implemented) to a null build object. The panic has been fixed in this release. - Fix incorrect location of certain error messages ([#​3845](https://redirect.github.com/evanw/esbuild/issues/3845)) This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild. - Print comments before case clauses in switch statements ([#​3838](https://redirect.github.com/evanw/esbuild/issues/3838)) With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification). - Fix a memory leak with `pluginData` ([#​3825](https://redirect.github.com/evanw/esbuild/issues/3825)) With this release, the build context's internal `pluginData` cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return `pluginData` objects from `onResolve` and/or `onLoad` callbacks. ### [`v0.23.0`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230) [Compare Source](https://redirect.github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. - Revert the recent change to avoid bundling dependencies for node ([#​3819](https://redirect.github.com/evanw/esbuild/issues/3819)) This release reverts the recent change in version 0.22.0 that made `--packages=external` the default behavior with `--platform=node`. The default is now back to `--packages=bundle`. I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future. In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development. - Fix preserving collapsed JSX whitespace ([#​3818](https://redirect.github.com/evanw/esbuild/issues/3818)) When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is an example: ```jsx // Original code // Old output (with --jsx=preserve) ; // New output (with --jsx=preserve) ; ``` ### [`v0.22.0`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220) [Compare Source](https://redirect.github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. - Omit packages from bundles by default when targeting node ([#​1874](https://redirect.github.com/evanw/esbuild/issues/1874), [#​2830](https://redirect.github.com/evanw/esbuild/issues/2830), [#​2846](https://redirect.github.com/evanw/esbuild/issues/2846), [#​2915](https://redirect.github.com/evanw/esbuild/issues/2915), [#​3145](https://redirect.github.com/evanw/esbuild/issues/3145), [#​3294](https://redirect.github.com/evanw/esbuild/issues/3294), [#​3323](https://redirect.github.com/evanw/esbuild/issues/3323), [#​3582](https://redirect.github.com/evanw/esbuild/issues/3582), [#​3809](https://redirect.github.com/evanw/esbuild/issues/3809), [#​3815](https://redirect.github.com/evanw/esbuild/issues/3815)) This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for `--platform=node`) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use `--packages=external` to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this. With this release, esbuild will now omit packages from the bundle by default when the platform is `node` (i.e. the previous behavior of `--packages=external` is now the default in this case). *Note that your dependencies must now be present on the file system when your bundle is run.* If you don't want this behavior, you can do `--packages=bundle` to allow packages to be included in the bundle (i.e. the previous default behavior). Note that `--packages=bundle` doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using `--external:` even when `--packages=bundle` is present. The `--packages=` setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of `/` or `.` or `..` are considered to be package imports. The only two exceptions to this rule are [subpath imports](https://nodejs.org/api/packages.html#subpath-imports) (which start with a `#` character) and TypeScript path remappings via `paths` and/or `baseUrl` in `tsconfig.json` (which are applied first). - Drop support for older platforms ([#​3802](https://redirect.github.com/evanw/esbuild/issues/3802)) This release drops support for the following operating systems: - Windows 7 - Windows 8 - Windows Server 2008 - Windows Server 2012 This is because the Go programming language dropped support for these operating system versions in [Go 1.21](https://go.dev/doc/go1.21#windows), and this release updates esbuild from Go 1.20 to Go 1.22. Note that this only affects the binary esbuild executables that are published to the `esbuild` npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this: git clone https://github.com/evanw/esbuild.git cd esbuild go build ./cmd/esbuild ./esbuild.exe --version In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's [release schedule](https://nodejs.org/en/about/previous-releases) for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the `esbuild-wasm` package and versions of node before node 17.4 (specifically the `crypto.getRandomValues` function). - Update `await using` behavior to match TypeScript TypeScript 5.5 subtly changes the way `await using` behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in [microsoft/TypeScript#58624](https://redirect.github.com/microsoft/TypeScript/pull/58624). - Allow `es2024` as a target environment The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: . The only addition that's relevant for esbuild is the regular expression `/v` flag. With `--target=es2024`, regular expressions that use the `/v` flag will now be passed through untransformed instead of being transformed into a call to `new RegExp`. - Publish binaries for OpenBSD on 64-bit ARM ([#​3665](https://redirect.github.com/evanw/esbuild/issues/3665), [#​3674](https://redirect.github.com/evanw/esbuild/pull/3674)) With this release, you should now be able to install the `esbuild` npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip. This was contributed by [@​ikmckenz](https://redirect.github.com/ikmckenz). - Publish binaries for WASI (WebAssembly System Interface) preview 1 ([#​3300](https://redirect.github.com/evanw/esbuild/issues/3300), [#​3779](https://redirect.github.com/evanw/esbuild/pull/3779)) The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a `.wasm` file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access). Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has [released support for preview 1](https://go.dev/blog/wasi), which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them. This release publishes esbuild precompiled for WASI preview 1 to the `@esbuild/wasi-preview1` package on npm (specifically the file `@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1. - Warn about `onResolve` plugins not setting a path ([#​3790](https://redirect.github.com/evanw/esbuild/issues/3790)) Plugins that return values from `onResolve` without resolving the path (i.e. without setting either `path` or `external: true`) will now cause a warning. This is because esbuild only uses return values from `onResolve` if it successfully resolves the path, and it's not good for invalid input to be silently ignored. - Add a new Go API for running the CLI with plugins ([#​3539](https://redirect.github.com/evanw/esbuild/pull/3539)) With esbuild's Go API, you can now call `cli.RunWithPlugins(args, plugins)` to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled. This was contributed by [@​edewit](https://redirect.github.com/edewit).
oxc-project/oxc (oxc-transform) ### [`v0.30.4`](https://redirect.github.com/oxc-project/oxc/blob/HEAD/npm/oxc-transform/CHANGELOG.md#0304---2024-09-28) ##### Documentation - [`26a273a`](https://redirect.github.com/oxc-project/oxc/commit/26a273a) oxc-transform: Update README (Boshen) - [`e2c5baf`](https://redirect.github.com/oxc-project/oxc/commit/e2c5baf) transformer: Fix formatting of README ([#​6111](https://redirect.github.com/oxc-project/oxc/issues/6111)) (overlookmotel) ### [`v0.30.3`](https://redirect.github.com/oxc-project/oxc/blob/HEAD/npm/oxc-transform/CHANGELOG.md#0303---2024-09-27) ##### Documentation - [`6167f29`](https://redirect.github.com/oxc-project/oxc/commit/6167f29) oxc-transform: Modify the example code in the `Readme` file ([#​6103](https://redirect.github.com/oxc-project/oxc/issues/6103)) (loong.woo) ### [`v0.28.0`](https://redirect.github.com/oxc-project/oxc/blob/HEAD/npm/oxc-transform/CHANGELOG.md#0280---2024-09-11) ##### Styling - [`694f032`](https://redirect.github.com/oxc-project/oxc/commit/694f032) Add trailing line breaks to `package.json` files ([#​5542](https://redirect.github.com/oxc-project/oxc/issues/5542)) (overlookmotel) ### [`v0.27.0`](https://redirect.github.com/oxc-project/oxc/compare/bd7499dc7173fc903857dba496e8a37f522b275d...64eb2cccb7f9db7708caa84f830abb675830f120) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/bd7499dc7173fc903857dba496e8a37f522b275d...64eb2cccb7f9db7708caa84f830abb675830f120) ### [`v0.26.0`](https://redirect.github.com/oxc-project/oxc/blob/HEAD/npm/oxc-transform/CHANGELOG.md#0260---2024-09-03) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/0b900110a23eee931f529b887019010d7dd41c5e...bd7499dc7173fc903857dba496e8a37f522b275d) ##### Features - [`72740b3`](https://redirect.github.com/oxc-project/oxc/commit/72740b3) isolated_declaration: Support sourcemap option ([#​5170](https://redirect.github.com/oxc-project/oxc/issues/5170)) (dalaoshu) ### [`v0.25.0`](https://redirect.github.com/oxc-project/oxc/blob/HEAD/npm/oxc-transform/CHANGELOG.md#0250---2024-08-23) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/5d0fb979cb8b0c06045b1df91e23b9157097ea4c...0b900110a23eee931f529b887019010d7dd41c5e) ##### Bug Fixes - [`2a5e15d`](https://redirect.github.com/oxc-project/oxc/commit/2a5e15d) npm: `libc` field should not be `null` (Boshen) ### [`v0.24.3`](https://redirect.github.com/oxc-project/oxc/compare/977b74af2dbb7693a37585b5aaf0a83431cc8c5a...5d0fb979cb8b0c06045b1df91e23b9157097ea4c) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/977b74af2dbb7693a37585b5aaf0a83431cc8c5a...5d0fb979cb8b0c06045b1df91e23b9157097ea4c) ### [`v0.24.2`](https://redirect.github.com/oxc-project/oxc/compare/857bc733029cc4d5cd29b0f1bc99cb02ed6441e1...977b74af2dbb7693a37585b5aaf0a83431cc8c5a) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/857bc733029cc4d5cd29b0f1bc99cb02ed6441e1...977b74af2dbb7693a37585b5aaf0a83431cc8c5a) ### [`v0.24.1`](https://redirect.github.com/oxc-project/oxc/compare/e02bac357afdc69c4d65e7642d704fae65e2c68d...857bc733029cc4d5cd29b0f1bc99cb02ed6441e1) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/e02bac357afdc69c4d65e7642d704fae65e2c68d...857bc733029cc4d5cd29b0f1bc99cb02ed6441e1) ### [`v0.23.0`](https://redirect.github.com/oxc-project/oxc/compare/80118cbf3b62496e440d0362ad3d4a3e9ad2e6fb...e02bac357afdc69c4d65e7642d704fae65e2c68d) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/80118cbf3b62496e440d0362ad3d4a3e9ad2e6fb...e02bac357afdc69c4d65e7642d704fae65e2c68d) ### [`v0.22.1`](https://redirect.github.com/oxc-project/oxc/compare/00c7b7dad449b59e59a6638960b22a05ae57008b...80118cbf3b62496e440d0362ad3d4a3e9ad2e6fb) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/00c7b7dad449b59e59a6638960b22a05ae57008b...80118cbf3b62496e440d0362ad3d4a3e9ad2e6fb) ### [`v0.22.0`](https://redirect.github.com/oxc-project/oxc/compare/0abcf499b7e2c7373ac0388953603ff1cdc719c4...00c7b7dad449b59e59a6638960b22a05ae57008b) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/0abcf499b7e2c7373ac0388953603ff1cdc719c4...00c7b7dad449b59e59a6638960b22a05ae57008b) ### [`v0.21.0`](https://redirect.github.com/oxc-project/oxc/compare/2a169d19693be273ec9fff6cc5dccb600b03cfab...0abcf499b7e2c7373ac0388953603ff1cdc719c4) [Compare Source](https://redirect.github.com/oxc-project/oxc/compare/2a169d19693be273ec9fff6cc5dccb600b03cfab...0abcf499b7e2c7373ac0388953603ff1cdc719c4)

Configuration

📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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



This PR was generated by Mend Renovate. View the repository job log.

coderabbitai[bot] commented 1 week ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
github-actions[bot] commented 1 week ago

Thank you for following the naming conventions! 🙏

socket-security[bot] commented 5 days ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@ckeditor/typedoc-plugins@44.1.1 filesystem 0 53.6 kB ckeditor

🚮 Removed packages: npm/@ckeditor/typedoc-plugins@44.0.0

View full report↗︎