mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
6538 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
depfu[bot]
|
f97d094813
|
Update bun 1.3.2 → 1.3.3 (patch) (#19413)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ bun (1.3.2 → 1.3.3) · [Repo](https://github.com/oven-sh/bun) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
b4f3d177fc
|
Update postcss-selector-parser 7.1.0 → 7.1.1 (patch) (#19408)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ postcss-selector-parser (7.1.0 → 7.1.1) · [Repo](https://github.com/postcss/postcss-selector-parser) · [Changelog](https://github.com/postcss/postcss-selector-parser/blob/master/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/postcss/postcss-selector-parser/releases/tag/v7.1.1">7.1.1</a></h4> <blockquote><h1 dir="auto">7.1.1</h1> <ul dir="auto"> <li>perf: replace startsWith with strict equality (<a href="https://bounce.depfu.com/github.com/postcss/postcss-selector-parser/pull/308">#308</a>)</li> <li>fix(types): add walkUniversal declaration (<a href="https://bounce.depfu.com/github.com/postcss/postcss-selector-parser/pull/311">#311</a>)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/postcss-selector-parser/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
Andrés
|
9c8cf8ac19
|
Fix formatting of path in README.md (#19407)
<!-- 👋 Hey, thanks for your interest in contributing to Tailwind! **Please ask first before starting work on any significant new features.** It's never a fun experience to have your pull request declined after investing a lot of time and effort into a new feature. To avoid this from happening, we request that contributors create a discussion to first discuss any significant new features. For more info, check out the contributing guide: https://github.com/tailwindcss/tailwindcss/blob/main/.github/CONTRIBUTING.md --> ## Summary quotation mark is not closed in README doc of the postcss preprocesor ## Test plan not needed |
||
|
depfu[bot]
|
a92fa97499 | Update all of nextjs to version 16.0.7 | ||
Jordan Pittman
|
a5f4644507
|
Validate named values in candidate parser (#19397)
Fixes https://github.com/tailwindlabs/tailwindcss-intellisense/issues/1506 |
||
|
Jordan Pittman
|
5f107e2822 | Fix typo | ||
Kirti Gautam
|
0d0d97d0cb
|
Fix invalid template tags in tests (#19400)
Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
depfu[bot]
|
7c69e83e81
|
Update @playwright/test 1.56.1 → 1.57.0 (minor) (#19399)
Here is everything you need to know about this update. Please take a
good look at what changed and the test results before merging this pull
request.
### What changed?
#### ✳️ @playwright/test (1.56.1 → 1.57.0) ·
[Repo](https://github.com/Microsoft/playwright)
<details>
<summary>Release Notes</summary>
<h4><a
href="https://github.com/microsoft/playwright/releases/tag/v1.57.0">1.57.0</a></h4>
<blockquote><h2 dir="auto">Speedboard</h2>
<p dir="auto">In HTML reporter, there's a new tab we call
"Speedboard":</p>
<a
href="https://private-user-images.githubusercontent.com/14912729/518585867-4ba117ea-ea94-4b6a-82b2-8bbd00dfe81c.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjQxNjA4MDQsIm5iZiI6MTc2NDE2MDUwNCwicGF0aCI6Ii8xNDkxMjcyOS81MTg1ODU4NjctNGJhMTE3ZWEtZWE5NC00YjZhLTgyYjItOGJiZDAwZGZlODFjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTExMjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMTI2VDEyMzUwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTY4YjhlYjY1ZTA1NGU5MjU5NjU5MDQzNDdhZjMzYmEzYjRlMTg2ZGJlZTA1YTA5NWQ3ODY4MTEzNTdlNWUwNTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.YQEEtVqnrOmR45G6zYUkuaOJL3k2DlbVb4cM0frrGQg"><img
width="600" alt="speedboard"
src="https://private-user-images.githubusercontent.com/14912729/518585867-4ba117ea-ea94-4b6a-82b2-8bbd00dfe81c.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjQxNjA4MDQsIm5iZiI6MTc2NDE2MDUwNCwicGF0aCI6Ii8xNDkxMjcyOS81MTg1ODU4NjctNGJhMTE3ZWEtZWE5NC00YjZhLTgyYjItOGJiZDAwZGZlODFjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTExMjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMTI2VDEyMzUwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTY4YjhlYjY1ZTA1NGU5MjU5NjU5MDQzNDdhZjMzYmEzYjRlMTg2ZGJlZTA1YTA5NWQ3ODY4MTEzNTdlNWUwNTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.YQEEtVqnrOmR45G6zYUkuaOJL3k2DlbVb4cM0frrGQg"
style="max-width: 100%;"></a>
<p dir="auto">It shows you all your executed tests sorted by
slowness,<br>
and can help you understand where your test suite is taking longer than
expected.<br>
Take a look at yours - maybe you'll find some tests that are spending a
longer time waiting than they should!</p>
<h2 dir="auto">Chrome for Testing</h2>
<p dir="auto">Starting with this release, Playwright switches from
Chromium, to using <a
href="https://developer.chrome.com/blog/chrome-for-testing/">Chrome for
Testing</a> builds. Both headed and headless browsers are subject to
this. Your tests should still be passing after upgrading to Playwright
1.57.</p>
<p dir="auto">We're expecting no functional changes to come from this
switch. The biggest change is the new icon and title in your
toolbar.</p>
<a
href="https://private-user-images.githubusercontent.com/14912729/518586000-e9a5c4f2-9f35-4c27-9382-0f5eda377097.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjQxNjA4MDQsIm5iZiI6MTc2NDE2MDUwNCwicGF0aCI6Ii8xNDkxMjcyOS81MTg1ODYwMDAtZTlhNWM0ZjItOWYzNS00YzI3LTkzODItMGY1ZWRhMzc3MDk3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTExMjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMTI2VDEyMzUwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ3YWFkMTAzM2I0YmQ1MDU4ODRlMDA0YzQ2NjQ3YjRlZjJkYTA4MmY5YTdlYzBmZmE1ZWI4NDk0NzQ2YTdiMGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.IPnNJmILND-iF20WnvLwMZQZMteYB8WFNIPXNL-lofc"><img
width="500" alt="new and old logo"
src="https://private-user-images.githubusercontent.com/14912729/518586000-e9a5c4f2-9f35-4c27-9382-0f5eda377097.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjQxNjA4MDQsIm5iZiI6MTc2NDE2MDUwNCwicGF0aCI6Ii8xNDkxMjcyOS81MTg1ODYwMDAtZTlhNWM0ZjItOWYzNS00YzI3LTkzODItMGY1ZWRhMzc3MDk3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTExMjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMTI2VDEyMzUwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ3YWFkMTAzM2I0YmQ1MDU4ODRlMDA0YzQ2NjQ3YjRlZjJkYTA4MmY5YTdlYzBmZmE1ZWI4NDk0NzQ2YTdiMGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.IPnNJmILND-iF20WnvLwMZQZMteYB8WFNIPXNL-lofc"
style="max-width: 100%;"></a>
<p dir="auto">If you still see an unexpected behaviour change, please <a
href="https://bounce.depfu.com/github.com/microsoft/playwright/issues/new">file
an issue</a>.</p>
<p dir="auto">On Arm64 Linux, Playwright continues to use Chromium.</p>
<h2 dir="auto">Waiting for webserver output</h2>
<p dir="auto"><a
href="https://playwright.dev/docs/api/class-testconfig#test-config-web-server">testConfig.webServer</a>
added a <code class="notranslate">wait</code> field. Pass a regular
expression, and Playwright will wait until the webserver logs match
it.</p>
<div class="highlight highlight-source-js" dir="auto"><pre
class="notranslate"><span class="pl-k">import</span> <span
class="pl-kos">{</span> <span class="pl-s1">defineConfig</span> <span
class="pl-kos">}</span> <span class="pl-k">from</span> <span
class="pl-s">'@playwright/test'</span><span class="pl-kos">;</span>
<span class="pl-k">export</span> <span class="pl-k">default</span> <span
class="pl-en">defineConfig</span><span class="pl-kos">(</span><span
class="pl-kos">{</span>
<span class="pl-c1">webServer</span>: <span class="pl-kos">{</span>
<span class="pl-c1">command</span>: <span class="pl-s">'npm run
start'</span><span class="pl-kos">,</span>
<span class="pl-c1">wait</span>: <span class="pl-kos">{</span>
<span class="pl-c1">stdout</span>: <span class="pl-s">'/Listening on
port (?<my_server_port>\\d+)/'</span>
<span class="pl-kos">}</span><span class="pl-kos">,</span>
<span class="pl-kos">}</span><span class="pl-kos">,</span>
<span class="pl-kos">}</span><span class="pl-kos">)</span><span
class="pl-kos">;</span></pre></div>
<p dir="auto">If you include a named capture group into the expression,
then Playwright will provide the capture group contents via environment
variables:</p>
<div class="highlight highlight-source-js" dir="auto"><pre
class="notranslate"><span class="pl-k">import</span> <span
class="pl-kos">{</span> <span class="pl-s1">test</span><span
class="pl-kos">,</span> <span class="pl-s1">expect</span> <span
class="pl-kos">}</span> <span class="pl-k">from</span> <span
class="pl-s">'@playwright/test'</span><span class="pl-kos">;</span>
<span class="pl-s1">test</span><span class="pl-kos">.</span><span
class="pl-en">use</span><span class="pl-kos">(</span><span
class="pl-kos">{</span> <span class="pl-c1">baseUrl</span>: <span
class="pl-s">`http://localhost:<span class="pl-s1"><span
class="pl-kos">${</span><span class="pl-s1">process</span><span
class="pl-kos">.</span><span class="pl-c1">env</span><span
class="pl-kos">.</span><span class="pl-c1">MY_SERVER_PORT</span> <span
class="pl-c1">??</span> <span class="pl-c1">3000</span><span
class="pl-kos">}</span></span>`</span> <span
class="pl-kos">}</span><span class="pl-kos">)</span><span
class="pl-kos">;</span>
<span class="pl-en">test</span><span class="pl-kos">(</span><span
class="pl-s">'homepage'</span><span class="pl-kos">,</span> <span
class="pl-k">async</span> <span class="pl-kos">(</span><span
class="pl-kos">{</span> page <span class="pl-kos">}</span><span
class="pl-kos">)</span> <span class="pl-c1">=></span> <span
class="pl-kos">{</span>
<span class="pl-k">await</span> <span class="pl-s1">page</span><span
class="pl-kos">.</span><span class="pl-en">goto</span><span
class="pl-kos">(</span><span class="pl-s">'/'</span><span
class="pl-kos">)</span><span class="pl-kos">;</span>
<span class="pl-kos">}</span><span class="pl-kos">)</span><span
class="pl-kos">;</span></pre></div>
<p dir="auto">This is not just useful for capturing varying ports of dev
servers. You can also use it to wait for readiness of a service that
doesn't expose an HTTP readiness check, but instead prints a readiness
message to stdout or stderr.</p>
<h2 dir="auto">Breaking Change</h2>
<p dir="auto">After 3 years of being deprecated, we removed <code
class="notranslate">Page#accessibility</code> from our API. Please use
other libraries such as <a href="https://www.deque.com/axe/">Axe</a> if
you need to test page accessibility. See our Node.js <a
href="https://playwright.dev/docs/accessibility-testing">guide</a> for
integration with Axe.</p>
<h2 dir="auto">New APIs</h2>
<ul dir="auto">
<li>New property <a
href="https://playwright.dev/docs/api/class-testconfig#test-config-tag">testConfig.tag</a>
adds a tag to all tests in this run. This is useful when using <a
href="https://playwright.dev/docs/test-sharding#merging-reports-from-multiple-shards">merge-reports</a>.</li>
<li>
<a
href="https://playwright.dev/docs/api/class-worker#worker-event-console">worker.on('console')</a>
event is emitted when JavaScript within the worker calls one of console
API methods, e.g. console.log or console.dir. <a
href="https://playwright.dev/docs/api/class-worker#worker-wait-for-event">worker.waitForEvent()</a>
can be used to wait for it.</li>
<li>
<a
href="https://playwright.dev/docs/api/class-locator#locator-description">locator.description()</a>
returns locator description previously set with <a
href="https://playwright.dev/docs/api/class-locator#locator-describe">locator.describe()</a>,
and <code class="notranslate">Locator.toString()</code> now uses the
description when available.</li>
<li>New option <a
href="https://playwright.dev/docs/api/class-locator#locator-click-option-steps"><code
class="notranslate">steps</code></a> in <a
href="https://playwright.dev/docs/api/class-locator#locator-click">locator.click()</a>
and <a
href="https://playwright.dev/docs/api/class-locator#locator-drag-to">locator.dragTo()</a>
that configures the number of <code class="notranslate">mousemove</code>
events emitted while moving the mouse pointer to the target
element.</li>
<li>Network requests issued by <a
href="https://playwright.dev/docs/service-workers#network-events-and-routing">Service
Workers</a> are now reported and can be routed through the <a
href="https://playwright.dev/docs/api/class-browsercontext">BrowserContext</a>,
only in Chromium. You can opt out using the <code
class="notranslate">PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK</code>
environment variable.</li>
<li>Console messages from Service Workers are dispatched through <a
href="https://playwright.dev/docs/api/class-worker#worker-event-console">worker.on('console')</a>.
You can opt out of this using the <code
class="notranslate">PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE</code>
environment variable.</li>
</ul>
<h2 dir="auto">Browser Versions</h2>
<ul dir="auto">
<li>Chromium 143.0.7499.4</li>
<li>Mozilla Firefox 142.0.1</li>
<li>WebKit 26.0</li>
</ul></blockquote>
<p><em>Does any of this look wrong? <a
href="https://depfu.com/packages/npm/@playwright%2Ftest/feedback">Please
let us know.</a></em></p>
</details>
<details>
<summary>Commits</summary>
<p><a
href="
|
||
Robin Malfait
|
229121dd14
|
Canonicalization: combine text-* and leading-* classes (#19396)
This PR improves the canonicalization when using `text-*` and `leading-*` utilities together. When using classes such as: ```html <div class="text-sm leading-7"></div> ``` Then the canonical way of writing this is: ```html <div class="text-sm/7"></div> ``` Similarly, if you already have a modifier applied, and add a new line-height utility. It will also combine them into the canonical form: ```html <div class="text-sm/6 leading-7"></div> ``` becomes: ```html <div class="text-sm/7"></div> ``` This is because the final CSS output of `text-sm/6 leading-7` is: ```css /*! tailwindcss v4.1.16 | MIT License | https://tailwindcss.com */ .text-sm\/6 { font-size: var(--text-sm, 0.875rem); line-height: calc(var(--spacing, 0.25rem) * 6); } .leading-7 { --tw-leading: calc(var(--spacing, 0.25rem) * 7); line-height: calc(var(--spacing, 0.25rem) * 7); } @property --tw-leading { syntax: "*"; inherits: false; } ``` Where the `line-height` of the `leading-7` class wins over the `line-height` of the `text-sm/6` class. ### Implementation #### On the fly pre-computation Right now, we are not using any AST based transformations yet and instead rely on a pre-computed list. However, with arbitrary values we don't have pre-computed values for `text-sm/123` for example. What we do instead is if we see a utility that sets `line-height` and other utilities set `font-size` then we pre-compute those computations on the fly. We will prefer named font-sizes (such as `sm`, `lg`, etc). We will also prefer bare values for line-height (such as `7`) over arbitrary values (such as `[123px]`). #### Canonicalization of the CSS AST Another thing we had to do is to make sure that when multiple declarations of the same property exist, that we only keep the last one. In the real world, multiple declarations of the same value is typically used for fallback values (e.g.: `background-color: #fff; background-color: oklab(255 255 255 / 1);`). But for our use case, I believe we can safely remove the earlier declarations to make the most modern and thus the last declaration win. #### Trying combinations based on `property` only One small change we had to make is that we try combinations of utilities based on property only instead of property _and_ value. This is important for cases such as `text-sm/6 leading-7`. These 2 classes will set a `lin-height` of `24px` and `28px` respectively so they will never match. However, once combined together, there will be 2 line-height values, and the last one wins. The signature of `text-sm/6 leading-7` becomes: ```css .x { font-size: 14px; /* From text-sm/6 */ line-height: 24px; /* From text-sm/6 */ line-height: 28px; /* From leading-7 */ } ``` ↓↓↓↓↓↓↓↓↓ ```css .x { font-size: 14px; /* From text-sm/6 */ line-height: 28px; /* From leading-7 */ } ``` This now shows that just `text-sm/7` is the canonical form. Because it produces the same final CSS output. ## Test plan 1. All existing tests pass 2. Added a bunch of new tests where we combine `text-*` and `leading-*` utilities with named, bare and arbitrary values. Even with existing modifiers on the text utilities. <img width="1010" height="1099" alt="image" src="https://github.com/user-attachments/assets/d2775692-a442-4604-8371-21dacf16ebfc" /> |
||
|
Jordan Pittman
|
243615e3f2
|
Handle backwards compatibility for content theme from JS configs (#19381)
Fixes #19343 This PR makes it so the `content-*` utilities read from the `--content-*` theme namespace. This change is **purely for backwards compatibility with Tailwind CSS v3**. It is recommended you use arbitrary values with the `content-*` utility instead. |
||
|
Jordan Pittman
|
764275143e
|
Improve compatibility with special default values in JS configs (#19348)
Fixes #19345 In v3 the `ringColor.DEFAULT` option was used as the default color for ring utilities (when it was defined). This currently gets translated as `--ring-color` but that doesn't work this way in v4. Instead it should translate to `--default-ring-color` and *not* `--ring-color`. I've also tweaked the upgrade tool to handle this properly as well. |
||
|
Robin Malfait
|
af481175e7
|
remove unnecessary intermediate check | ||
|
Robin Malfait
|
9e436f7751
|
Try to canonicalize any arbitrary utility to a bare value (#19379)
This PR adds an improvement to our canonicalization logic when dealing with arbitrary values. When trying to canonicalize utilities, we make use of the intellisense suggestions list where we typically use multiples of the spacing scale. This means that a value like `gap-[128px]` gets properly canonicalized to `gap-32`. However, when you try a value that we typically don't suggest such as `gap-[116px]` then it doesn't get canonicalized at all. This PR fixes that by trying to use the spacing scale and convert `116px / 4px` and try the `gap-29` utility instead. This is done by canonicalizing the incoming arbitrary value and the spacing multipliers such that `--spacing: 0.25rem` and `--spacing: 4px` both work as expected. ### Test plan 1. Added some tests with a spacing scale of `0.25rem` (which is the default) 2. Added some tests with the same spacing scale in a different unit `4px` 3. Added some tests with a different spacing scale `1px` Also had to update 1 test that now gets canonicalized properly, e.g.: `w-[124px]` → `w-31`. |
||
|
Jordan Pittman
|
117433a100 |
Revert "Update globby 15.0.0 → 16.0.0 (major) (#19357)"
This reverts commit 28670a9b91033b6361a73b7e42c15da96fa96409. |
||
|
Jordan Pittman
|
0e8f075ca2
|
Fix source map generation during when watching files on the CLI (#19373)
Fixes #19362 We were overwriting the source map with the "decoded" map returned by the compiler but didn't wrap it in the helper intended to help inline vs file maps. This resulted in two issues: 1. `undefined` being appended to the CSS file when using `--map` 2. `undefined` being passed to `writeFile(…)` when using `--map <file>` This PR fixes both. |
||
|
depfu[bot]
|
28670a9b91
|
Update globby 15.0.0 → 16.0.0 (major) (#19357)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ globby (15.0.0 → 16.0.0) · [Repo](https://github.com/sindresorhus/globby) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/sindresorhus/globby/releases/tag/v16.0.0">16.0.0</a></h4> <blockquote><h3 dir="auto">Breaking</h3> <ul dir="auto"> <li>Respect parent .gitignore files when <code class="notranslate">gitignore</code> option is enabled <a href=" |
||
|
depfu[bot]
|
a1f533a0e0 | Update @emnapi/core to version 1.7.1 | ||
|
depfu[bot]
|
385edfb80d
|
Update emnapi 1.6.0 → 1.7.1 (minor) (#19351)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ emnapi (1.6.0 → 1.7.1) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.7.1">1.7.1</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>move Node-API version detection by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/182">#182</a> </li> <li>feat: support SharedArrayBuffer in napi_create_dataview by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/183">#183</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.7.0...v1.7.1"><tt>v1.7.0...v1.7.1</tt></a></p></blockquote> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.7.0">1.7.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: add napi_create_object_with_properties method by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/181">#181</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.6.0...v1.7.0"><tt>v1.6.0...v1.7.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/emnapi/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
251fe27658
|
Update @vitejs/plugin-react 5.1.0 → 5.1.1 (patch) (#19355)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @vitejs/plugin-react (5.1.0 → 5.1.1) · [Repo](https://github.com/vitejs/vite-plugin-react) · [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4>5.1.1 (from changelog)</h4> <blockquote><h3 dir="auto">Update code to support newer <code class="notranslate">rolldown-vite</code> (<a href="https://bounce.depfu.com/github.com/vitejs/vite-plugin-react/pull/976">#976</a>)</h3> <p dir="auto"><code class="notranslate">rolldown-vite</code> will remove <code class="notranslate">optimizeDeps.rollupOptions</code> in favor of <code class="notranslate">optimizeDeps.rolldownOptions</code> soon. This plugin now uses <code class="notranslate">optimizeDeps.rolldownOptions</code> to support newer <code class="notranslate">rolldown-vite</code>. Please update <code class="notranslate">rolldown-vite</code> to the latest version if you are using an older version.</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@vitejs%2Fplugin-react/feedback">Please let us know.</a></em></p> </details> ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
98d221f24b
|
Update @emnapi/runtime 1.6.0 → 1.7.1 (minor) (#19349)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @emnapi/runtime (1.6.0 → 1.7.1) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.7.1">1.7.1</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>move Node-API version detection by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/182">#182</a> </li> <li>feat: support SharedArrayBuffer in napi_create_dataview by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/183">#183</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.7.0...v1.7.1"><tt>v1.7.0...v1.7.1</tt></a></p></blockquote> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.7.0">1.7.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: add napi_create_object_with_properties method by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/181">#181</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.6.0...v1.7.0"><tt>v1.6.0...v1.7.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@emnapi%2Fruntime/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
Robin Malfait
|
479b725cd3
|
Bump Vitest to v4 (#19216)
This PR bumps Vitest from v2 to v4. As far as I know we don't use any Vitest specific features in our tests, but had to upgrade the `vitest.workspace.ts` file to a `vitest.config.ts` file instead. The only features we use are the typical `describe`, `it`, `test`, and `expect` functions. The only other part we use is `vi.spyOn` and `vi.fn` but those didn't change in API either. The test shards were removed to prevent errors. Not all suites have enough files / tests to be broken up into 3 parts so Vitest now errors when that happens. ### Test plan 1. All tests should pass in CI. 2. All integration tests should pass in CI. --------- Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
Jordan Pittman
|
642b9b8576
|
Don’t unconditionally convert config keys to kebab-case (#19337)
Fixes #18114 Closes #18115 This PR changes JS config handling such that we always preserve casing for theme keys (when possible). Now there are *two* exceptions to this rule: 1. Top-level keys in the theme *do* get converted to kebab-case. As CSS variables are not generated from these this shouldn't be a big issue. All of our internal plugins look for kebab-case keys. So, for example, take the path `backgroundColor.red.500`. This must translate to `--background-color-red-500`. But if you had something like `backgroundColor.lightBlue` it would be perfectly fine for that to translate to `--background-color-lightBlue` internally (and thus the utility be written as `bg-lightBlue`. 2. Tuple object keys are converted to kebab-case as well. These keys are converted to "nested" key syntax internally and typtically represent CSS property names. For example: ```js export default { theme: { fontSize: { xs: ["1.5rem", { lineHeight: "1.3" }] }, fontFamily: { sans: ["Potato Mono", { fontVariationSettings: '"XHGT" 0.7' }] } } } ``` The `lineHeight` key here must be converted to `line-height` because it represents a CSS property name. The theme key that represents this value is `--text-xs--line-height`. The same situation applies for the `fontVariationSettings` where the theme key is `--font-sans--font-variation-settings`. |
||
|
Jordan Pittman
|
5a8e878319
|
Handle future and experimental config keys during upgrade (#19344)
Fixes #19342 |
||
|
depfu[bot]
|
68337df3db | Update @types/bun to version 1.3.2 | ||
|
depfu[bot]
|
7c0eeaa3a6
|
Update all of nextjs 15.5.6 → 16.0.3 (major) (#19341)
Here is everything you need to know about this upgrade. Please take a
good look at what changed and the test results before merging this pull
request.
### What changed?
#### ✳️ eslint-config-next (15.5.6 → 16.0.3)
Sorry, we couldn't find anything useful about this release.
#### ✳️ next (15.5.6 → 16.0.3) ·
[Repo](https://github.com/vercel/next.js)
<details>
<summary>Release Notes</summary>
<h4><a
href="https://github.com/vercel/next.js/releases/tag/v16.0.3">16.0.3</a></h4>
<blockquote><em>More info than we can show here.</em></blockquote>
<h4><a
href="https://github.com/vercel/next.js/releases/tag/v16.0.2">16.0.2</a></h4>
<blockquote><em>More info than we can show here.</em></blockquote>
<h4><a
href="https://github.com/vercel/next.js/releases/tag/v16.0.1">16.0.1</a></h4>
<blockquote><em>More info than we can show here.</em></blockquote>
<h4><a
href="https://github.com/vercel/next.js/releases/tag/v16.0.0">16.0.0</a></h4>
<blockquote><em>More info than we can show here.</em></blockquote>
<p><em>Does any of this look wrong? <a
href="https://depfu.com/packages/npm/next/feedback">Please let us
know.</a></em></p>
</details>
<details>
<summary>Commits</summary>
<p><a
href="
|
||
|
depfu[bot]
|
172c663bd6
|
Update tsup 8.5.0 → 8.5.1 (patch) (#19338)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ tsup (8.5.0 → 8.5.1) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
3d899f73f8 | Update @types/react-dom to version 19.2.3 | ||
|
depfu[bot]
|
5f243dbb0f
|
Update bun 1.3.0 → 1.3.2 (patch) (#19334) | ||
|
Jordan Pittman
|
a7c968efb1
|
bump turbo (#19179)
The Bun build issue was caused by Turborepo passing through `USERPROFILE` from the env. Probably need to file a bug with Bun: ``` Works: env: USERPROFILE: undefined CWD: `D:\a\tailwindcss\tailwindcss\packages\@tailwindcss-standalone` Fails: env: USERPROFILE: "C:\Users\runneradmin" CWD: `D:\a\tailwindcss\tailwindcss\packages\@tailwindcss-standalone` ``` |
||
|
Jordan Pittman
|
e4b6c67bcb
|
Support Vite Environment API (#18970)
Fixes #18002 Very much a work in progress b/c I don't (yet) understand how the newer APIs are intended to function. - [x] Needs env specific tests that verify the environment API is being used |
||
|
depfu[bot]
|
c532955dd1
|
Update autoprefixer 10.4.21 → 10.4.22 (patch) (#19322)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ autoprefixer (10.4.21 → 10.4.22) · [Repo](https://github.com/postcss/autoprefixer) · [Changelog](https://github.com/postcss/autoprefixer/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/postcss/autoprefixer/releases/tag/10.4.22">10.4.22</a></h4> <blockquote><ul dir="auto"> <li>Fixed <code class="notranslate">stretch</code> prefixes on new Can I Use database.</li> <li>Updated <code class="notranslate">fraction.js</code>.</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/autoprefixer/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
Alexander Lichter
|
21f2bf99b9
|
perf(vite): add plugin hook filter (#19308)
## Summary This PR adds plugin [hook filters](https://vite.dev/guide/api-plugin#hook-filters) to the Vite plugin. They are backwards-compatible, having no impact on older Vite versions as the check for `isPotentialCssRootFile` is still included. It can be dropped once you don't need to support older Vite versions. ## See also https://github.com/e18e/ecosystem-issues/issues/171 --------- Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
Jordan Pittman
|
4455051c48
|
Skip comments in Ruby files when checking for class names (#19243)
Fixes #19239 |
||
Ishita SIngh
|
5bc90dd2e0
|
Include filename and line numbers in CSS parse errors (#19282)
Co-authored-by: Jordan Pittman <jordan@cryptica.me> |
||
|
depfu[bot]
|
5a89571efd
|
Update eslint 9.37.0 → 9.39.1 (minor) (#19287)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint (9.37.0 → 9.39.1) · [Repo](https://github.com/eslint/eslint) · [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/eslint/eslint/releases/tag/v9.39.1">9.39.1</a></h4> <blockquote><h2 dir="auto">Bug Fixes</h2> <ul dir="auto"> <li> <a href=" |
||
|
Jordan Pittman
|
4363426384
|
Fix validation of source(…) paths (#19274)
Fixes #18833 - [x] Needs tests Basically we were correctly resolving the path given to `source()` inside Oxide *but* inside `@tailwindcss/node` when we validated that the path was a directory we were not. We incorrectly used the base path of the input file rather than the file the `source(…)` directive was defined in. This PR fixes that. |
||
|
Jordan Pittman
|
e9c9c4f79d
|
Release v4.1.17 (#19272) v4.1.17 | ||
|
Jordan Pittman
|
dc6a3ce349
|
Substitute @variant inside utilities (#19263)
Fixes #19258 |
||
Hongxu Xu
|
babe825f2d
|
Remove unused crossbeam dependency in oxide (#19256)
|
||
|
depfu[bot]
|
3e4654d7ea
|
Update @types/react-dom 19.2.1 → 19.2.2 (patch) (#19259)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @types/react-dom (19.2.1 → 19.2.2) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
3cece1d97c | Update @napi-rs/cli to version 3.4.1 | ||
|
depfu[bot]
|
604c22f25e
|
Update @vitejs/plugin-react 5.0.4 → 5.1.0 (minor) (#19241)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @vitejs/plugin-react (5.0.4 → 5.1.0) · [Repo](https://github.com/vitejs/vite-plugin-react) · [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4>5.1.0 (from changelog)</h4> <blockquote><h3 dir="auto">Add <code class="notranslate">@vitejs/plugin-react/preamble</code> virtual module for SSR HMR (<a href="https://bounce.depfu.com/github.com/vitejs/vite-plugin-react/pull/890">#890</a>)</h3> <p dir="auto">SSR applications can now initialize HMR runtime by importing <code class="notranslate">@vitejs/plugin-react/preamble</code> at the top of their client entry instead of manually calling <code class="notranslate">transformIndexHtml</code>. This simplifies SSR setup for applications that don't use the <code class="notranslate">transformIndexHtml</code> API.</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@vitejs%2Fplugin-react/feedback">Please let us know.</a></em></p> </details> ---  [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> |
||
|
depfu[bot]
|
e71e70eda9
|
Update magic-string 0.30.19 → 0.30.21 (minor) (#19238)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ magic-string (0.30.19 → 0.30.21) · [Repo](https://github.com/rich-harris/magic-string) · [Changelog](https://github.com/Rich-Harris/magic-string/blob/master/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/Rich-Harris/magic-string/releases/tag/v0.30.21">0.30.21</a></h4> <blockquote><p dir="auto"><em>No significant changes</em></p> <h5 dir="auto"> <a href="https://bounce.depfu.com/github.com/Rich-Harris/magic-string/compare/v0.30.20...v0.30.21">View changes on GitHub</a> </h5></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/magic-string/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
4827c465b8
|
Update @emnapi/core 1.5.0 → 1.6.0 (minor) (#19220)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @emnapi/core (1.5.0 → 1.6.0) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.6.0">1.6.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: added SharedArrayBuffer api by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/171">#171</a> </li> <li>feat: make napi_delete_reference use node_api_basic_env by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/170">#170</a> </li> <li>ci: migrate to npm trusted publishing by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/168">#168</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.5.0...v1.6.0"><tt>v1.5.0...v1.6.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@emnapi%2Fcore/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
4aa763b2a3
|
Update emnapi 1.5.0 → 1.6.0 (minor) (#19221)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ emnapi (1.5.0 → 1.6.0) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.6.0">1.6.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: added SharedArrayBuffer api by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/171">#171</a> </li> <li>feat: make napi_delete_reference use node_api_basic_env by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/170">#170</a> </li> <li>ci: migrate to npm trusted publishing by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/168">#168</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.5.0...v1.6.0"><tt>v1.5.0...v1.6.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/emnapi/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
7bab613749
|
Update @emnapi/runtime 1.5.0 → 1.6.0 (minor) (#19219)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @emnapi/runtime (1.5.0 → 1.6.0) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.6.0">1.6.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: added SharedArrayBuffer api by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/171">#171</a> </li> <li>feat: make napi_delete_reference use node_api_basic_env by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/170">#170</a> </li> <li>ci: migrate to npm trusted publishing by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/168">#168</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.5.0...v1.6.0"><tt>v1.5.0...v1.6.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@emnapi%2Fruntime/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
depfu[bot]
|
91694fbfc1 | Update @playwright/test to version 1.56.1 | ||
|
depfu[bot]
|
effcd27e17
|
Update all of nextjs 15.5.4 → 15.5.6 (patch) (#19194)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint-config-next (15.5.4 → 15.5.6) Sorry, we couldn't find anything useful about this release. #### ✳️ next (15.5.4 → 15.5.6) · [Repo](https://github.com/vercel/next.js) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.5.6">15.5.6</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>Turbopack: don't define process.cwd() in node_modules <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/83452">#83452</a> </li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/mischnic">@mischnic</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.5.5">15.5.5</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>Split code-frame into separate compiled package (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84238">#84238</a>)</li> <li>Add deprecation warning to Runtime config (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84650">#84650</a>)</li> <li>fix: unstable_cache should perform blocking revalidation during ISR revalidation (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84716">#84716</a>)</li> <li>feat: <code class="notranslate">experimental.middlewareClientMaxBodySize</code> body cloning limit (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84722">#84722</a>)</li> <li>fix: missing next/link types with typedRoutes (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84779">#84779</a>)</li> </ul> <h3 dir="auto">Misc Changes</h3> <ul dir="auto"> <li>docs: early October improvements and fixes (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84334">#84334</a>)</li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/devjiwonchoi">@devjiwonchoi</a>, <a href="https://bounce.depfu.com/github.com/ztanner">@ztanner</a>, and <a href="https://bounce.depfu.com/github.com/icyJoseph">@icyJoseph</a> for helping!</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/next/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href=" |
||
|
Robin Malfait
|
2530934a4f
|
update changelog | ||
|
Robin Malfait
|
cbbbe84475
|
Release 4.1.16 (#19185) v4.1.16 |
