feat: always-fresh production tarballs + Nuxt DevTools production playground - #511
Merged
Conversation
Extract the pack/rename logic behind the production playground's pack-local.mjs into a shared scripts/pack-devtools-tarballs.mjs, and fold the install step into the script itself: every run now wipes .tarballs/, repacks from scratch, and reinstalls with --force so a freshly rebuilt tarball is never mistaken for a stale previous install.
…vTools Introduce a standalone pnpm workspace running Nuxt 5 (nightly channel) with Nuxt DevTools 4, whose internal @vitejs/devtools and @vitejs/devtools-kit dependencies are overridden via pnpm.overrides to the local built dist tarballs (packed the same way as the production playground). This exercises the other real-world install path: Nuxt DevTools v4 embeds Vite DevTools as its own engine, so this validates that the build under test runs correctly there, not just when mounted directly as a Vite plugin.
@vitejs/devtools
@vitejs/devtools-kit
@vitejs/devtools-oxc
@vitejs/devtools-rolldown
@vitejs/devtools-vite
@vitejs/devtools-vitest
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Two changes to the standalone
playgrounds/*install-path tests:playgrounds/production/scripts/pack-local.mjsalways packs the latest tarballs and installs from them. Previously packing and installing were separate steps, and a rebuilt tarball under the same stable filename could be mistaken for the previous stale install by pnpm's store cache (the README even documented a manual--forceworkaround). The pack/rename logic is now shared viascripts/pack-devtools-tarballs.mjs, and the script always finishes with a forcedpnpm install --no-frozen-lockfile --force, so every run wipes.tarballs/, repacks from scratch, and reinstalls fresh — no stale tarballs or stale installs left behind.New
playgrounds/production-nuxtplayground, mirroringplaygrounds/productionbut for the other real-world install path: Nuxt DevTools. Nuxt DevTools v4 (@nuxt/devtools@^4.0.0-alpha.9) depends directly on@vitejs/devtoolsand@vitejs/devtools-kit, embedding Vite DevTools as its own engine. This playground runs Nuxt 5 (via Nuxt's nightly channel,npm:nuxt-nightly@5x, since Nuxt 5 isn't on stable dist-tags yet) with Nuxt DevTools 4, and usespnpm.overridesto force Nuxt DevTools' internal@vitejs/devtools/-kit(and every sibling package) to the local built dist tarballs — so it validates the build under test running inside Nuxt DevTools, not just as a standalone Vite plugin.Linked Issues
Additional context
playgrounds/production-nuxtis excluded from the rootpnpm-workspace.yamland the repo-wide ESLint run, the same wayplaygrounds/productionalready is, since it's a standalone workspace with its own lockfile and plain (non-catalog) dependency specifiers.🤖 Created with the help of an AI agent