Skip to content

Move to vite based build system to be able to keep site up to date with security vuls #1523

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

Draft
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

karianna
Copy link
Member

No description provided.

Copy link

netlify bot commented May 13, 2025

Deploy Preview for vibrant-hugle-19d716 ready!

Name Link
🔨 Latest commit 2133b6a
🔍 Latest deploy log https://app.netlify.com/sites/vibrant-hugle-19d716/deploys/6822f0580ab1210008250317
😎 Deploy Preview https://deploy-preview-1523--vibrant-hugle-19d716.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@gdams
Copy link
Member

gdams commented May 13, 2025

nice refactor! I see two issues though:

  1. The release assets aren't loading on the page: https://deploy-preview-1523--vibrant-hugle-19d716.netlify.app/archive
  2. Images don't seem to be rendering for me, is it the same on your side? I think for this one you need to move all the images in src/assets into the public folder.

Copy link
Member

Choose a reason for hiding this comment

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

guessing this isn't needed

Copy link
Member

Choose a reason for hiding this comment

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

guessing this isn't needed

@karianna
Copy link
Member Author

nice refactor! I see two issues though:

  1. The release assets aren't loading on the page: https://deploy-preview-1523--vibrant-hugle-19d716.netlify.app/archive
  2. Images don't seem to be rendering for me, is it the same on your side? I think for this one you need to move all the images in src/assets into the public folder.

Yeah oddly these both work fine for me locally when running npm run dev, so I suspect a subtle deploy difference there.

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