wrapper/tailwindcss
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions
tailwindcss/playgrounds/nextjs/package.json

25 lines
522 B
JSON
Raw Permalink Normal View History

introduce v4 codebase
2024-03-05 14:23:26 +01:00
{
"name": "nextjs-playground",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
Bump Next.js and drop ESLint (#19898) This PR bumps Next.js and drops ESLint. We only had ESLint installed because it came with `next lint`. We don't actively use ESLint, it was just used in the playgrounds where we test things out. Dropping this reduces the amount of dependencies we have to deal with. Closes: #19867 Closes: #19852 # Test plan Tested both the `nextjs` and `v3` playgrounds after bumping the Next.js dependency and getting rid of ESLint, and they still work as expected.
2026-04-03 21:07:27 +02:00
"start": "next start"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
},
"dependencies": {
"@tailwindcss/postcss": "workspace:^",
Update fast-glob 3.3.2 → 3.3.3 (patch) (#15607)
2025-01-13 11:11:35 +01:00
"fast-glob": "^3.3.3",
Update next 16.2.6 → 16.2.7 (patch) (#20207) 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? #### ✳️ next (16.2.6 → 16.2.7) · [Repo](https://github.com/vercel/next.js) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vercel/next.js/releases/tag/v16.2.7">16.2.7</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg data-component="Octicon" 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>Backport documentation fixes for v16.2 (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/93804">#93804</a>)</li> <li>[backport] Patch <code class="notranslate">playwright-core</code> to resolve <code class="notranslate">_finishedPromise</code> on <code class="notranslate">requestFailed</code> (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/93920">#93920</a>)</li> <li>[backport] Fix dev mode hydration failure when page is served from HTTP cache (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/93492">#93492</a>)</li> <li>[backport] Fix catch-all <code class="notranslate">router.query</code> corruption with <code class="notranslate">basePath</code> + <code class="notranslate">rewrites</code> (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/93917">#93917</a>)</li> <li>[backport] Encode non-ASCII characters in cache tags at construction (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/93918">#93918</a>)</li> <li>[backport] Fix server action forwarding loop with middleware rewrites (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/93919">#93919</a>)</li> <li>[backport] Turbopack: switch from base40 to base38 hash encoding (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/93932">#93932</a>)</li> <li>[ci] Disable hanging node 24 typescript tests on 16.2 backport branch (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/94164">#94164</a>)</li> <li>[backport] Fix "type: module" in project dir when using standalone or adapters (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/94050">#94050</a>)</li> <li>[backport] Propagate adapter preferred regions (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/94200">#94200</a>)</li> <li>[16.2.x] Don't drop <code class="notranslate">FormData</code> entries (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/94240">#94240</a>)</li> <li>[backport] feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/94284">#94284</a>)</li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/eps1lon">@eps1lon</a>, <a href="https://bounce.depfu.com/github.com/icyJoseph">@icyJoseph</a>, <a href="https://bounce.depfu.com/github.com/unstubbable">@unstubbable</a>, <a href="https://bounce.depfu.com/github.com/mischnic">@mischnic</a>, <a href="https://bounce.depfu.com/github.com/bgw">@bgw</a>, <a href="https://bounce.depfu.com/github.com/timneutkens">@timneutkens</a>, and <a href="https://bounce.depfu.com/github.com/lukesandberg">@lukesandberg</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="https://github.com/vercel/next.js/compare/ee6e79b1792a4d401ddf2480f40a83549fe8e722...9bd3c26a733901956549889f28c0047553bba622">See the full diff on Github</a>. The new version differs by 13 commits:</p> <ul> <li><a href="https://github.com/vercel/next.js/commit/9bd3c26a733901956549889f28c0047553bba622"><code>v16.2.7</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/c63224f3d8e8dd0a4ef8635916f92954421e5f1e"><code>[backport] feat(turbopack): add LocalPathOrProjectPath PostCSS config resolution (#94284)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/63115c79877c90df4371c2425f3fc5d3a55ac58d"><code>[16.2.x] Don&#39;t drop `FormData` entries (#94240)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/aef22fdc828226227f618bb982a222e1256ba6f2"><code>[backport] Propagate adapter preferred regions (#94200)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/f126e72271a808a12adb1f97feca6a900bece7ba"><code>[backport] Fix &quot;type: module&quot; in project dir when using standalone or adapters (#94050)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/bda3e2aabe5ba18b6e8ec656bcdaf549816469c3"><code>[ci] Disable hanging node 24 typescript tests on 16.2 backport branch (#94164)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/7e16e07c0203f8a940899e656526f287278c57e6"><code>[backport] Turbopack: switch from base40 to base38 hash encoding (#93932)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/6139f4b885b329abdd5821199cc19cc89f3eaf33"><code>[backport] Fix server action forwarding loop with middleware rewrites (#93919)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/c021d10fe9540aaa7aff7b7227c7d73e60a0e5b9"><code>[backport] Encode non-ASCII characters in cache tags at construction (#93918)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/9184ddb1aeed5c5db0f02c7a2d6d298071c2f44f"><code>[backport] Fix catch-all `router.query` corruption with `basePath` + `rewrites` (#93917)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/3279f01607e646edb4457061ed2a819a24b314a5"><code>[backport] Fix dev mode hydration failure when page is served from HTTP cache (#93492)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/ffc4f29682d427d2e27c1d26e178fede57b00123"><code>[backport] Patch `playwright-core` to resolve `_finishedPromise` on `requestFailed` (#93920)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/bc1791dd7e31059db09a449e46bacb1364dec994"><code>Backport documentation fixes for v16.2 (#93804)</code></a></li> </ul> </details> --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [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>
2026-06-09 12:38:33 +02:00
"next": "16.2.7",
Update all of react 19.2.6 → 19.2.7 (patch) (#20206) <!--depfu-start--> > 👉 **This PR is queued up to get rebased by Depfu** <!--depfu-end--> 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? #### ✳️ react (19.2.6 → 19.2.7) · [Repo](https://github.com/facebook/react) · [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/facebook/react/releases/tag/v19.2.7">19.2.7</a></h4> <blockquote><h2 dir="auto">React Server Components</h2> <ul dir="auto"> <li>Fixed missing <code class="notranslate">FormData</code> entries in Server Actions which regressed in 19.2.6<br> (<a href="https://bounce.depfu.com/github.com/facebook/react/pull/36566">#36566</a> by <a href="https://bounce.depfu.com/github.com/unstubbable">@unstubbable</a>)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/react/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/facebook/react/compare/eaf3e95ca92be7a23d3c9cc8ffd6f199a40be401...6117d7cca4906492c51fe6a03381e35adfd86e7d">See the full diff on Github</a>. The new version differs by 5 commits:</p> <ul> <li><a href="https://github.com/facebook/react/commit/6117d7cca4906492c51fe6a03381e35adfd86e7d"><code>Version 19.2.7 (#36591)</code></a></li> <li><a href="https://github.com/facebook/react/commit/53a07de1a783f040b6ebc202a993358598dab65e"><code>[19.2.x] Unified release process (#36550)</code></a></li> <li><a href="https://github.com/facebook/react/commit/02c444c3f01d90ca9cb98fa53bb17d98ac12e2a8"><code>[19.2.x][FlightReply] Don&#39;t drop FormData entries in `decodeReplyFromBusboy` (#36566)</code></a></li> <li><a href="https://github.com/facebook/react/commit/750848e565bb657a4759cf7f6efb17fb82e674a6"><code>[19.2.x][ci] Create artifact attestations for builds on backport branches (#36559)</code></a></li> <li><a href="https://github.com/facebook/react/commit/e1cfa7b6decef7082b664b54df420ae7dfc69d11"><code>[19.2.x] Enable CI (#36552)</code></a></li> </ul> </details> --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [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>
2026-06-09 10:44:01 +00:00
"react": "19.2.7",
"react-dom": "19.2.7",
introduce v4 codebase
2024-03-05 14:23:26 +01:00
"tailwindcss": "workspace:^"
},
"devDependencies": {
Upgrade vitest and remove bench script from CI (#14101) This PR updates vitest to v2. The changes are mostly around using fork instead of threads for how tests are run which should fix one of the issues we've found. Ever since adding the unit tests on Windows, we started seeing occacional flags of vitest crashing with the following error: ```  ELIFECYCLE  Command failed with exit code 3221225477. Error: Process completed with exit code 1. ``` When reading the [v2 changelog](https://github.com/vitest-dev/vitest/releases/tag/v2.0.0) we saw many bug fixes related to segfaulting so we believe this was the issue. When upgrading `vitest` alone, we got a bunch of dependency mismatches though (specifically, vite was installed two times with different peer dependencies for `@types/node` which causes our vite plugin's `Plugin` type to be different from the one in the vite playground. Yikes. These were eventually fixed by having pnpm create a new lockfile for us. So, unfortunatly this PR also bumps a bunch of patch versions for some transitive dependencies. Tests seem fine, though 🤞 This PR also removes the `bench` script from CI. It doesn't give us value in its current state (since it's not reporting when performance regresses) but added a few seconds of unnecessary overhead to each test run.
2024-08-02 10:33:14 +02:00
"@types/node": "catalog:",
Bump dependencies (#20095) This PR bumps some of our dependencies, common dependencies were moved to pnpm's `catalog` feature. Closes #20092 Closes #20085 Closes #20075 Closes #20066 Closes #20062 ## Test plan - All tests still pass - Each dependency was published some time ago. Webpack has an even newer version that was published <15min ago. Will update that one later. [ci-all]
2026-05-21 17:58:55 +02:00
"@types/react": "19.2.15",
Bump Next.js and drop ESLint (#19898) This PR bumps Next.js and drops ESLint. We only had ESLint installed because it came with `next lint`. We don't actively use ESLint, it was just used in the playgrounds where we test things out. Dropping this reduces the amount of dependencies we have to deal with. Closes: #19867 Closes: #19852 # Test plan Tested both the `nextjs` and `v3` playgrounds after bumping the Next.js dependency and getting rid of ESLint, and they still work as expected.
2026-04-03 21:07:27 +02:00
"@types/react-dom": "19.2.3",
Bump dependencies in playgrounds (#19954) This PR bumps dependencies in our playgrounds. Closes: https://github.com/tailwindlabs/tailwindcss/pull/19952 Closes: https://github.com/tailwindlabs/tailwindcss/pull/19945 ### Test plan Ran each playground separately to make sure they are still working
2026-04-23 12:51:20 +02:00
"typescript": "^6.0.3"
introduce v4 codebase
2024-03-05 14:23:26 +01:00
}
}
Reference in a new issue Copy permalink