-
-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: moving to vite + typescript #352
Merged
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
Vite proxying now works again, had to disable CSRF protection during development.
|
Cant' get package version to work |
Fixed PWA + package version ! |
WDaan
changed the title
perf: moving to vite + typescript
feat!: moving to vite + typescript
Nov 15, 2022
WDaan
added a commit
that referenced
this pull request
Nov 15, 2022
This was referenced Nov 15, 2022
This was referenced Nov 6, 2023
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.
Vite
Move to Vite for faster build times and to remove lot of unneeded and deprecated packages.
This PR is actually quite important because right now the project is a little stuck.
node-sass/sass/sass-loader is icompatible with nodejs 16+
vue-cli-service with webpack is slow
I want to move to Vite, because it's a lot faster, but there are still some issues:
Proxying post requests is not working=> solvedI also cant move the project to Vue3, because it relies heavily on Vuetify which does not support Vue3 yet.
PR Checklist