Repository navigation
fix(deps): update dependency vite-plus to v1.1.0 - #28
Closed
renovate[bot] wants to merge 2 commits into
Closed
renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
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
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.
This PR contains the following updates:
1.0.0→1.1.0Release Notes
voidzero-dev/vite-plus (vite-plus)
v1.1.0: vite-plus v1.1.0: fastervp devstartup and clearer interactive promptsCompare Source
Vite+ 1.1 starts
vp devfaster and makes the interactive prompts clearer, alongside fixes forvp migrate, package-manager commands, and Windows terminals.Highlights
vp devreaches its local URL about 24% sooner and uses about 30% less memory in the parent process, because Vite+ no longer loads Vite and Vitest there before starting the dev server (#2851), by @camc314.Features
vp runsetsnpm_execpathandnpm_config_user_agentfor npm, pnpm, and Yarn, so tools such as npm-run-all2 use the project's package manager instead of falling back to npm (#2895), by @naokihaba and @tarikermis.vite@8.3.1tovite@8.3.3,rolldown@1.2.11torolldown@1.2.12,vitest@5.0.1tovitest@5.0.3,oxlint@1.85.0tooxlint@1.87.0, andoxfmt@0.70.0tooxfmt@0.72.0. The new lint and format versions can flag code that passed before, so runvp fmtafter upgrading if CI runsvp check.vp migratenow keeps the React RefreshallowCompoundComponentsoption because the bundled Oxlint supports it (#2871, #2896, #2904), by @voidzero-guard[bot].Fixes & Enhancements
vp migratekeeps Oxlint rules written with plugin aliases (such as@typescript-eslint/*,react-hooks/*, andimport-x/*) and removes rules the bundled Oxlint does not support, listing them in a warning (#2820, #2906), by @TheAlexLichter and @yusuke99.vp migrateleaves projects without a declared package manager unpinned, keeps existing declarations, and points tovp env pinwhen it infers one (#2817), by @TheAlexLichter.vp migratereports a short error for a directory withoutpackage.jsoninstead of anENOENTstack trace (#2821), by @TheAlexLichter.vp createin an existing pnpm workspace adds the catalog entries the new application needs, so installation no longer fails withERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC(#2808), by @SaKaNa-Y.vprscripts and managed Bun, pnpm, npm, and Yarn commands without leavingcmd.exestuck atTerminate batch job (Y/N)?(#2890), by @fengmk2.vp pack --watchon Windows rebuilds with the new options after the config file changes (#2826), by @liangmiQwQ.vp test doctorandvp test completerun the Vitest subcommands instead of being treated as test file filters (#2879), by @liangmiQwQ.vp packfinds installed Vue language tools and TypeScript Go for declaration generation, and Playwright browser provider options keep their types (#2868, #2865), by @liangmiQwQ.--offlineand--prefer-offline, and Yarn Classic accepts a single--filterforvp remove(#2775), by @jong-kyung.vp pm configin Bun projects falls back to npm, as its warning says (#2899), by @jong-kyung.vp pm approve-buildsstates that Yarn Berry disables third-party build scripts by default from 4.14.0, not in every version (#2902), by @jong-kyung.vp implodeasks you to typeboominstead ofuninstallto confirm (#2901), by @fengmk2.+, and removals a red-, with bold package names in both (#2828), by @liangmiQwQ.Refactor
semverwithverkitin the CLI, reducing the bundled CLI JavaScript by about 26 KB (#2837), by @liangmiQwQ.vp env doctor, and remove unused config migration metadata (#2876, #2894), by @jong-kyung.Docs
vp packdemo (#2843, #2844), by @TheAlexLichter and @naokihaba.vp install -g --nodeand explain whenvp env defaultre-resolves versions (#2885, #2884), by @hyunbinseo.vpxguide andvpx --help(#2864), by @SaKaNa-Y.vp installstep fromsetup-vpCI examples (#2888), by @yusuke99.vp env current --jsonexample for the split directory layout (#2886, #2887, #2889, #2891), by @jong-kyung.Chore
docs/public, and ignore the roottmpdirectory (#2832, #2831, #2860), by @liangmiQwQ.set-snapshot-versionaction (#2877), by @jong-kyung.Bundled Versions
8.3.3fea5b211.2.1245e407b0.23.05.0.31.87.07.0.20030.72.0Upgrade
New Contributors
@hyunbinseo
Full Changelog: voidzero-dev/vite-plus@v1.0.0...v1.1.0
Published Packages
@voidzero-dev/vite-plus-core@1.1.0vite-plus@1.1.0Installation
macOS/Linux:
curl -fsSL https://vite.plus | bashWindows:
Or download and run
vp-setup.exefrom the assets below.Docker:
docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:1.1.0 vp buildRun any
vpcommand without installing it; see the Docker guide for more.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.