Skip to content
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

chore(webapp): migrate to vite 5 #837

Merged
merged 5 commits into from
Jan 8, 2024

Conversation

Rotzbua
Copy link
Contributor

@Rotzbua Rotzbua commented Nov 19, 2023

Guide

https://vitejs.dev/guide/migration.html

Changes

  • Migrate to vite v5
  • Change build to ESM
  • Update CSP hash for legacy support
  • Fix sass warnings and eslint error

@peterthomassen
Copy link
Member

Closes #805

@Rotzbua
Copy link
Contributor Author

Rotzbua commented Dec 26, 2023

@peterthomassen Works for me. Can you review? Happy xmas 🎄

Copy link
Member

@peterthomassen peterthomassen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks mostly good; just minor stuff.

According to https://vitejs.dev/guide/migration#allow-path-containing-to-fallback-to-index-html, this also fixes #805. Can you confirm that's the case?

www/webapp/package.json Show resolved Hide resolved
test/e2e2/spec/test_www.py Outdated Show resolved Hide resolved
@peterthomassen
Copy link
Member

Happy xmas 🎄

Same to you, very much belated! And happy new year! 🥳

Copy link
Member

@peterthomassen peterthomassen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks a lot!

Because old `vuetify` is used. `sass` can be bumped if whole webapp is migrated to vue@v3 and according vuetify.
Hash updated with new release v5.2 of `@vitejs/plugin-legacy`.
@peterthomassen peterthomassen merged commit 8ce07b2 into desec-io:main Jan 8, 2024
5 checks passed
@Rotzbua Rotzbua deleted the chore_migrate_vite_5 branch January 8, 2024 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants