tj/commander.js
### [`v9.4.1`](https://togithub.com/tj/commander.js/blob/HEAD/CHANGELOG.md#941-2022-09-30)
[Compare Source](https://togithub.com/tj/commander.js/compare/v9.4.0...v9.4.1)
##### Fixed
- `.setOptionValue()` now also clears option source (\[[#1795](https://togithub.com/tj/commander.js/issues/1795)])
- TypeScript: add `implied` to `OptionValueSource` for option values set by using `.implies()` (\[[#1794](https://togithub.com/tj/commander.js/issues/1794)])
- TypeScript : add `undefined` to return type of `.getOptionValueSource()` (\[[#1794](https://togithub.com/tj/commander.js/issues/1794)])
##### Changed
- additions to README
evanw/esbuild
### [`v0.15.10`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01510)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.9...v0.15.10)
- Add support for node's "pattern trailers" syntax ([#2569](https://togithub.com/evanw/esbuild/issues/2569))
After esbuild implemented node's `exports` feature in `package.json`, node changed the feature to also allow text after `*` wildcards in patterns. Previously the `*` was required to be at the end of the pattern. It lets you do something like this:
```json
{
"exports": {
"./features/*": "./features/*.js",
"./features/*.js": "./features/*.js"
}
}
```
With this release, esbuild now supports these types of patterns too.
- Fix subpath imports with Yarn PnP ([#2545](https://togithub.com/evanw/esbuild/issues/2545))
Node has a little-used feature called [subpath imports](https://nodejs.org/api/packages.html#subpath-imports) which are package-internal imports that start with `#` and that go through the `imports` map in `package.json`. Previously esbuild had a bug that caused esbuild to not handle these correctly in packages installed via Yarn's "Plug'n'Play" installation strategy. The problem was that subpath imports were being checked after Yarn PnP instead of before. This release reorders these checks, which should allow subpath imports to work in this case.
- Link from JS to CSS in the metafile ([#1861](https://togithub.com/evanw/esbuild/issues/1861), [#2565](https://togithub.com/evanw/esbuild/issues/2565))
When you import CSS into a bundled JS file, esbuild creates a parallel CSS bundle next to your JS bundle. So if `app.ts` imports some CSS files and you bundle it, esbuild will give you `app.js` and `app.css`. You would then add both `` and `` to your HTML to include everything in the page. This approach is more efficient than having esbuild insert additional JavaScript into `app.js` that downloads and includes `app.css` because it means the browser can download and parse both the CSS and the JS in parallel (and potentially apply the CSS before the JS has even finished downloading).
However, sometimes it's difficult to generate the `` tag. One case is when you've added `[hash]` to the [entry names](https://esbuild.github.io/api/#entry-names) setting to include a content hash in the file name. Then the file name will look something like `app-GX7G2SBE.css` and may change across subsequent builds. You can tell esbuild to generate build metadata using the `metafile` API option but the metadata only tells you which generated JS bundle corresponds to a JS entry point (via the `entryPoint` property), not which file corresponds to the associated CSS bundle. Working around this was hacky and involved string manipulation.
This release adds the `cssBundle` property to the metafile to make this easier. It's present on the metadata for the generated JS bundle and points to the associated CSS bundle. So to generate the HTML tags for a given JS entry point, you first find the output file with the `entryPoint` you are looking for (and put that in a ` Githubissues.
Githubissues is a development platform for aggregating issues.
This PR contains the following updates:
16.11.61->16.11.639.4.0->9.4.10.15.9->0.15.104.6.0->4.7.020.0.0->20.0.14.8.3->4.8.4Release Notes
tj/commander.js
### [`v9.4.1`](https://togithub.com/tj/commander.js/blob/HEAD/CHANGELOG.md#941-2022-09-30) [Compare Source](https://togithub.com/tj/commander.js/compare/v9.4.0...v9.4.1) ##### Fixed - `.setOptionValue()` now also clears option source (\[[#1795](https://togithub.com/tj/commander.js/issues/1795)]) - TypeScript: add `implied` to `OptionValueSource` for option values set by using `.implies()` (\[[#1794](https://togithub.com/tj/commander.js/issues/1794)]) - TypeScript : add `undefined` to return type of `.getOptionValueSource()` (\[[#1794](https://togithub.com/tj/commander.js/issues/1794)]) ##### Changed - additions to READMEevanw/esbuild
### [`v0.15.10`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01510) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.9...v0.15.10) - Add support for node's "pattern trailers" syntax ([#2569](https://togithub.com/evanw/esbuild/issues/2569)) After esbuild implemented node's `exports` feature in `package.json`, node changed the feature to also allow text after `*` wildcards in patterns. Previously the `*` was required to be at the end of the pattern. It lets you do something like this: ```json { "exports": { "./features/*": "./features/*.js", "./features/*.js": "./features/*.js" } } ``` With this release, esbuild now supports these types of patterns too. - Fix subpath imports with Yarn PnP ([#2545](https://togithub.com/evanw/esbuild/issues/2545)) Node has a little-used feature called [subpath imports](https://nodejs.org/api/packages.html#subpath-imports) which are package-internal imports that start with `#` and that go through the `imports` map in `package.json`. Previously esbuild had a bug that caused esbuild to not handle these correctly in packages installed via Yarn's "Plug'n'Play" installation strategy. The problem was that subpath imports were being checked after Yarn PnP instead of before. This release reorders these checks, which should allow subpath imports to work in this case. - Link from JS to CSS in the metafile ([#1861](https://togithub.com/evanw/esbuild/issues/1861), [#2565](https://togithub.com/evanw/esbuild/issues/2565)) When you import CSS into a bundled JS file, esbuild creates a parallel CSS bundle next to your JS bundle. So if `app.ts` imports some CSS files and you bundle it, esbuild will give you `app.js` and `app.css`. You would then add both `` and `` to your HTML to include everything in the page. This approach is more efficient than having esbuild insert additional JavaScript into `app.js` that downloads and includes `app.css` because it means the browser can download and parse both the CSS and the JS in parallel (and potentially apply the CSS before the JS has even finished downloading). However, sometimes it's difficult to generate the `` tag. One case is when you've added `[hash]` to the [entry names](https://esbuild.github.io/api/#entry-names) setting to include a content hash in the file name. Then the file name will look something like `app-GX7G2SBE.css` and may change across subsequent builds. You can tell esbuild to generate build metadata using the `metafile` API option but the metadata only tells you which generated JS bundle corresponds to a JS entry point (via the `entryPoint` property), not which file corresponds to the associated CSS bundle. Working around this was hacky and involved string manipulation. This release adds the `cssBundle` property to the metafile to make this easier. It's present on the metadata for the generated JS bundle and points to the associated CSS bundle. So to generate the HTML tags for a given JS entry point, you first find the output file with the `entryPoint` you are looking for (and put that in a ` Githubissues.