Upgrade wally.run to Parcel V2 #191
Closed
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
Dekkonot
reviewed
Oct 29, 2024
Dekkonot
added
merged to test
|
no |
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.
The wally.run registry site has started failing during automated deployment. Upon investigation, some extremely old packages seem to be the culprit, predominantly with how the Parcel bundler handlers
.mdxfiles. Most of the supporting packages in the Parcel ecosystem are now considered outdated and deprecated; the only provided suggestion across multiple NPM packages was to upgrade to Parcel V2.This PR bumps us from Parcel V1 (
parcel-bundler) to Parcel V2 (justparcel). It also required a suite of changes to config files and loaders. Most notably, we had to make some adjustments to how we load CSS modules to correctly parse them into the Markdown components.Additionally, while doing a visual regression comparison between the live site and this upgrade, I noticed a few glaring UI bugs that were either rough on the eyes or made the site more difficult for our keyboard/screen reader users. These weren't technically part of a regression, but they feel obtrusive enough to roll with these improvements. I've included those changes in the PR as well.