Add vite #109
Merged
Add vite #109
Conversation
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
|
|
|
I'm getting this error when I run the latest. Adding: to the package.json fixed it for me and things are working. Is anyone else running into this issue, or does adding this in work for everyone else? |
Author
|
I'm unable to reproduce the issue with the uuid package |
KeeyanGhoreshi
force-pushed
the
add-vite
branch
from
c736a42 to
ac7cd40
Compare
|
I just pulled down the latest and am no longer getting the uuid error @plarocque4 @KeeyanGhoreshi. Do you want to re-check if you are getting it now Pat? If not, we might be able to merge in as is! |
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.
Due to errors with using latest versions of Node and react-scripts, I've changed out react-scripts with something that is actually maintained in Vite. It should function identically to react-scripts, so everything should be the same as before, though there may be a couple of small bugs to iron out that I haven't detected with docker or deployment.