Vite integration #3
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi Benjamin Code 👋.
I offer you this PR which refers to this issue #1.
I have updated the development dependencies so that you can use ViteJS instead of ParcelJs ...
There is not much difference with Parcel but it could give you a plus (and I find Vitejs faster than Parcel).
Also with Vite, the hot-reload watches all the files you are working on.
Concretely, I configured the base of a Vite project for a quick start, I updated the README and fixed small minor things ... I hope that you will be interested and that you will appreciate 😀.
Que la force du code soit avec toi 🐱👤