feat: implement vite package bundler and fix previous webpack config

[mtfoley]

What type of PR is this? (check all applicable)

• ♻️ Refactor
• ✨ Feature
• 🐛 Bug Fix
• 👷 Optimization
• 📝 Documentation Update
• 🔖 Release
• 🚩 Other

Description

One could argue this closes #1131 😝 I managed to get things running in like 25 minutes because it had so many steps in common with PR #1320 💨

Related Tickets & Documents

closes #1346

Mobile & Desktop Screenshots/Recordings

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 readme
• 📜 contributing.md
• 📓 docs
• 📕 storybook
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

Pssh probably

[optional] What gif best describes this PR or how it makes you feel?

[0-vortex]

add closes # somewhere :D

[mtfoley]

Kinda sorta works at this point, but the service worker is broken, and that's breaking a lot of things in turn. Going to try some of what's in here: https://vite-plugin-pwa.netlify.app/guide/inject-manifest.html#custom-service-worker

[0-vortex]

adjusted the name of the PR to something more descriptive of what you're doing, now you can closes # the webpack issue 🍕

[mtfoley]

@0-vortex I can reproduce the error locally with node node_modules/vite/bin/vite.js preview after running a build. Per your suggestion, I tried this with https://github.com/vitejs/vite/tree/main/packages/plugin-react and it was even more messed up. I'm going to see if I can isolate a problematic component for now.

[0-vortex]

our .babelrc might have something to do with it as well!

[mtfoley]

So far it doesn’t appear to be an issue with the service worker (anymore), and at the moment the error seems to be somewhere in or near the react markdown component we use.

[0-vortex]

So far it doesn’t appear to be an issue with the service worker (anymore), and at the moment the error seems to be somewhere in or near the react markdown component we use.

Hope this is not a longshot but that honestly sounds much more reasonable, we might get some help around that by searching for the rollup keyword and our failing component :D

[mtfoley]

So far it doesn’t appear to be an issue with the service worker (anymore), and at the moment the error seems to be somewhere in or near the react markdown component we use.

This appears to be most likely related:
vitejs/vite#3592

cc @ajcwebdev since I know you were looking at this also.

[0-vortex]

LGTM! 👍

some minor improvement chores we can open issues for but keen to get this in 2021 still 🍕

[0-vortex]

@bdougie any chance you can check out this new technique?

[github-actions]

🎉 This PR is included in version 0.42.0 🎉

The release is available on:

• GitHub release
• ghcr.io container (@latest dist-tag)

Your semantic-release bot 📦🚀