35d8ea9fdbb6820e6377ef8ec809b2e7e38203eb
5 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Gregor Martynus
|
b287cb86e2 |
fix(deps): update @octokit packages to latest (#24)
|
||
|
dependabot[bot]
|
73a9531b26 |
build(deps-dev): bump dotenv from 16.0.3 to 16.3.1 (#18)
[//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [dotenv](https://github.com/motdotla/dotenv) from 16.0.3 to 16.3.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md">dotenv's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.3.0...v16.3.1">16.3.1</a> (2023-06-17)</h2> <h3>Added</h3> <ul> <li>Add missing type definitions for <code>processEnv</code> and <code>DOTENV_KEY</code> options. <a href="https://redirect.github.com/motdotla/dotenv/pull/756">#756</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.2.0...v16.3.0">16.3.0</a> (2023-06-16)</h2> <h3>Added</h3> <ul> <li>Optionally pass <code>DOTENV_KEY</code> to options rather than relying on <code>process.env.DOTENV_KEY</code>. Defaults to <code>process.env.DOTENV_KEY</code> <a href="https://redirect.github.com/motdotla/dotenv/pull/754">#754</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.4...v16.2.0">16.2.0</a> (2023-06-15)</h2> <h3>Added</h3> <ul> <li>Optionally write to your own target object rather than <code>process.env</code>. Defaults to <code>process.env</code>. <a href="https://redirect.github.com/motdotla/dotenv/pull/753">#753</a></li> <li>Add import type URL to types file <a href="https://redirect.github.com/motdotla/dotenv/pull/751">#751</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.3...v16.1.4">16.1.4</a> (2023-06-04)</h2> <h3>Added</h3> <ul> <li>Added <code>.github/</code> to <code>.npmignore</code> <a href="https://redirect.github.com/motdotla/dotenv/pull/747">#747</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.2...v16.1.3">16.1.3</a> (2023-05-31)</h2> <h3>Removed</h3> <ul> <li>Removed <code>browser</code> keys for <code>path</code>, <code>os</code>, and <code>crypto</code> in package.json. These were set to false incorrectly as of 16.1. Instead, if using dotenv on the front-end make sure to include polyfills for <code>path</code>, <code>os</code>, and <code>crypto</code>. <a href="https://github.com/Richienb/node-polyfill-webpack-plugin">node-polyfill-webpack-plugin</a> provides these.</li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.1...v16.1.2">16.1.2</a> (2023-05-31)</h2> <h3>Changed</h3> <ul> <li>Exposed private function <code>_configDotenv</code> as <code>configDotenv</code>. <a href="https://redirect.github.com/motdotla/dotenv/pull/744">#744</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.0...v16.1.1">16.1.1</a> (2023-05-30)</h2> <h3>Added</h3> <ul> <li>Added type definition for <code>decrypt</code> function</li> </ul> <h3>Changed</h3> <ul> <li>Fixed <code>{crypto: false}</code> in <code>packageJson.browser</code></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.0.3...v16.1.0">16.1.0</a> (2023-05-30)</h2> <h3>Added</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
bc0f04c81b |
build(deps): bump semver from 7.5.1 to 7.5.4 (#14)
Bumps [semver](https://github.com/npm/node-semver) from 7.5.1 to 7.5.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/npm/node-semver/releases">semver's releases</a>.</em></p> <blockquote> <h2>v7.5.4</h2> <h2><a href="https://github.com/npm/node-semver/compare/v7.5.3...v7.5.4">7.5.4</a> (2023-07-07)</h2> <h3>Bug Fixes</h3> <ul> <li><a href=" |
||
|
dependabot[bot]
|
1fc9983a3b |
build(deps-dev): bump esbuild from 0.17.19 to 0.19.2 (#19)
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.17.19 to 0.19.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p> <blockquote> <h2>v0.19.2</h2> <ul> <li> <p>Update how CSS nesting is parsed again</p> <p>CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:</p> <pre lang="css"><code>.foo { div { color: red; } } </code></pre> <p>Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.</p> <p>Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.</p> </li> <li> <p>Fix a scope-related bug with <code>--drop-labels=</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3311">#3311</a>)</p> <p>The recently-released <code>--drop-labels=</code> feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.</p> </li> <li> <p>Make renamed CSS names unique across entry points (<a href="https://redirect.github.com/evanw/esbuild/issues/3295">#3295</a>)</p> <p>Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.</p> </li> <li> <p>Fix CSS ordering bug with <code>@layer</code> before <code>@import</code></p> <p>CSS lets you put <code>@layer</code> rules before <code>@import</code> rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the <code>@import</code> rules and then joining files together in the right order. But with <code>@layer</code>, CSS files may now need to be split apart into multiple pieces in the bundle. For example:</p> <pre><code>/* Original code */ @layer start; @import "data:text/css,@layer inner.start;"; @import "data:text/css,@layer inner.end;"; @layer end; <p>/* Old output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> end;</p> <p>/* New output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> end; </code></pre></p> </li> <li> <p>Unwrap nested duplicate <code>@media</code> rules (<a href="https://redirect.github.com/evanw/esbuild/issues/3226">#3226</a>)</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>.</em></p> <blockquote> <h2>0.19.2</h2> <ul> <li> <p>Update how CSS nesting is parsed again</p> <p>CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:</p> <pre lang="css"><code>.foo { div { color: red; } } </code></pre> <p>Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.</p> <p>Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.</p> </li> <li> <p>Fix a scope-related bug with <code>--drop-labels=</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3311">#3311</a>)</p> <p>The recently-released <code>--drop-labels=</code> feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.</p> </li> <li> <p>Make renamed CSS names unique across entry points (<a href="https://redirect.github.com/evanw/esbuild/issues/3295">#3295</a>)</p> <p>Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.</p> </li> <li> <p>Fix CSS ordering bug with <code>@layer</code> before <code>@import</code></p> <p>CSS lets you put <code>@layer</code> rules before <code>@import</code> rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the <code>@import</code> rules and then joining files together in the right order. But with <code>@layer</code>, CSS files may now need to be split apart into multiple pieces in the bundle. For example:</p> <pre><code>/* Original code */ @layer start; @import "data:text/css,@layer inner.start;"; @import "data:text/css,@layer inner.end;"; @layer end; <p>/* Old output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> end;</p> <p>/* New output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> end; </code></pre></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
Gregor Martynus
|
f45685208f |
feat: initial version (#1)
Some checks failed
/ demo (push) Has been cancelled
Co-authored-by: Parker Brown <17183625+parkerbxyz@users.noreply.github.com> Co-authored-by: Gregor Martynus <gr2m@users.noreply.github.com> |