chore: Provide "playground" for custom render testing #2849
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
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.
Summary
This PR makes changes in order to support a "playground" area that can be taken advantage of on services such as stackblitz to create proof-of-concepts on issues/bugs/etc. Vite's dev feature is used for this. The
prepareandprepublishOnlylifecycle scripts were altered where testing/building happens onprepackwith only thehuskycommand being ran onprepare. This is to better align to the intent of when these commands are supposed to run (building the lib folder before packing/publishing) so that testing/building isn't immediately ran for justinstalloperations (this also fixes an issue with stackblitz where vite commands unfortunately break the environment when ran ininstall-related lifecycle scripts).How To Test
An example using stackblitz's pr.new can be seen here: https://pr.new/github.com/jpandersen87/react-uswds/tree/stackblitz