Conversation
0df3533 to
810879f
Compare
Member
Author
|
I think the migration is in good shape now. @mdo, could you take some time to go through all the use cases with me to make sure everything behaves as expected (i.e., the same as before)? In particular:
And anything else you think might be worth checking 🙏 |
mdo
approved these changes
Mar 21, 2026
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.
Local run
Note
I had to change the way
Scss.astroworked because the CSS was only loaded by the first page. Navigating to other pages didn't preserve the loaded CSS in the<head>. I don't know if this is an issue in Astro v6, but the new approach with the extradocs-dev.scsslooks rather well too.Local release build
Then go to
_siteand run a local server, likehttp-server.Netlify deployment
Our Netlify app must be configured with Node 20, which is not supported anymore by Astro
Not having the rights for the Netfliy config for Bootstrap, I ended up adding a
.nvmrcfile at the root of the project, that overrides the version set up in Netlify configuration.In the end, I would keep this
.nvmrcbecause it's really handy for contributors navigating between different projects to know which version of Node (+ npm) is actually used to build the project.Node 24
Since I needed to define a version in the
.nvmrc, I chose to use the latest LTS Node version, which is 24.14.0 (LTS); and bumped the version used in GitHub Actions files as well.Verification