-
-
Notifications
You must be signed in to change notification settings - Fork 3k
refactor: manifest as virtual module #14298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
fdc3bab to
f4db70b
Compare
9b7cb7d to
f0a6635
Compare
ascorbic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a good approach
packages/astro/test/units/vite-plugin-astro-server/request.test.js
Outdated
Show resolved
Hide resolved
2f18cc3 to
2868ab2
Compare
f17f70c to
4c16b50
Compare
|
I'll investigate later why the integration tests time out. I'll merge the PR for now |
* refactor: use environments to load modules (#14191) * refactor: make `App` more extensible using `BaseApp` (#14197) * refactor: App to extends the new BaseApp (#14213) * refactor: manifest as virtual module (#14298) * refactor: create `generate` when needed * fix type * remove type * fix types * fix breakage of code
Changes
This PR refactors how the manifest is computed and pulled during development and build.
There's a new module called
astro:serialized-manifest. While it returns a deserialised manifest, it's actually deserialised during its creation. It means that it's computed fromAstroSettings, and it's deserialised inside the virtual module.Happy to bikeshed the name.
Now
astro:config/serverandastro:config/clientuse this module to pull the information. Plus, I refactored them to usethis.environment.nameinstead ofopts.ssrTesting
Updated. They should all pass
Docs
N/A