-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
meta: Update Changelog for 7.83.0 #9684
Merged
Merged
Conversation
This file contains 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
…n individual packages (#9657)
This is code that isn't being used anywhere, and the code snippets are out of date (look at custom transport code). We can explore adding this back for v8.
[Gitflow] Merge master into develop
…9665) This PR adds support for uploading sourcemaps when using the `@astrojs/vercel/*` adapters. It seems that the adapter updates the config.outdir value too late for our previous detection logic to correctly detect the .vercel output directory. Furthermore, the adapter for some reason first saves server files to <root>/dist only to copy it later to <root>/.vercel/functions. This copy command seems to happen too late for when our sourcemaps plugin runs. For these two reasons, we try to detect the used adapter (love that this is much simpler in Astro than Sveltekit) and adjust the assets glob to search for files in both, `dist` and `.vercel`.
Astro 4.0.0 beta is out so let's adjust our peer deps! I opted for an open max version for now. THere's a risk of this being problematic with future major versions but I'd argue we'd get support requests either way. The important part IMO is the lower bound.
Adds the `assets` option to the Astro integration source maps upload options. It behaves just like the `assets` option of the Vite plugin, taking a (array of) glob(s) and overriding the default values. This came up in #9591 and I think it makes sense to give users with more advanced/custom setups the ability to override our defaults.
HazAT
approved these changes
Nov 28, 2023
HazAT
approved these changes
Nov 28, 2023
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.
17 more to go...