Conversation
🦋 Changeset detectedLatest commit: 685dbd9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
e18e dependency analysisNo dependency warnings found. |
# Conflicts: # packages/astro/src/core/build/static-build.ts
commit: |
This branch has not been deployed
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.
Changes
astro()fromastro/vite, so Astro runs as a regular Vite plugin: no Astro CLI, noastro.config.mjs. The Astro config, integrations included, is passed inline, andvite,vite buildandvite previewdo the work. Spike, draft only.astro()is called, because Vite collects plugins before itsconfighooks run: integration hooks run, thencreateVite, as in the CLI. The command is inferred fromNODE_ENV, or passed explicitly withdefineConfig((env) => ({ plugins: [astro(config, env)] })). Aconfighook throws if the guess doesn't match Vite's real command.vite.configonce per build environment, so the build-mode setup is cached per project root and cleared inbuildApp. Integration hooks run once, and every environment shares one set of plugin instances.astro:server:start/done→httpServerlistening/closeastro:build:done→buildApppost.astro/types work in dev and build. The dev content setup moves out ofcore/dev/dev.tsintocontent/dev-setup.ts, and the plugin reuses it.configureServer,buildAppandconfigurePreviewServer, not when the config is evaluated. Session events get a newsource: 'cli' | 'vite-plugin'field.commandfrom Vite.static-build.tsexposes the build environment config..astropages, React islands, live updates in dev, SSR with@astrojs/node, actions,astro:env, content collections,ClientRouter, and other Vite plugins alongside (Tailwind in the example).vite previewfor SSR output.vite previewasbuild.server.*options.add,check,sync).Testing
examples/vite-plugin-react, which uses@astrojs/react, a content collection and Tailwind, run withvite/vite build/vite preview.eventCliSession()unit tests for thesourcefield.Docs