4 ms·

Tangential but did you evaluate Snowpack and Vite? Both seem to share the same space and I was leaning towards Snowpack, but Vite now seems to have the mindshar

by porker 5y ago

Tangential but did you evaluate Snowpack and Vite? Both seem to share the same space and I was leaning towards Snowpack, but Vite now seems to have the mindshare. Which as a small dev shop is important when betting on it for 3+ years

richeyryan 5y ago
I trialed Snowpack earlier this year and found I ran into quite a lot of hard to debug issues. Around the same time I saw that Rich Harris, creator of Svelte and Sveltekit, opted to use Vite over Snowpack for Sveltekit because more things, like CSS and and SASS, just worked out of the box. I tried out Vite and it was a much smoother transition. As you said it seems to have more mindshare now and I would guess that is because the out of the box experience is better.
WorldMaker 5y ago
I've not tried Vite yet. I've been happy enough with snowpack so far, and they seem so similar in approach I haven't heard a reason to switch other than yes it does seem to be the new PR "hotness". Looking at Vite's own comparison I don't see a strong reason to switch that would impact most of my projects: https://vitejs.dev/guide/comparisons.html#snowpack https://vitejs.dev/guide/comparisons.html#snowpack But also I don't use Vue and I don't trust CSS Modules yet [1] which is their other most impactful feature of Vite. ([1] It still seems like reliable Browser support for CSS Modules is still 5 years away at the current rate, if it ever gets accepted as a standard. I don't think there's any obvious current objections and few browsers outside the Chromium hegemony to even really object today, but it's still one of those web standards that smells to me pessimistically like "it's never going to work right cross-browser", and even if I were less pessimistic about it, I prefer not to use them because I think they bloat CSS and subvert the intent behind cascading. At that point I think you might as well just use CSS-in-JS and that doesn't have to wait on web standards that may never arrive.)

by porker 5y ago

richeyryan 5y ago

I trialed Snowpack earlier this year and found I ran into quite a lot of hard to debug issues. Around the same time I saw that Rich Harris, creator of Svelte and Sveltekit, opted to use Vite over Snowpack for Sveltekit because more things, like CSS and and SASS, just worked out of the box. I tried out Vite and it was a much smoother transition. As you said it seems to have more mindshare now and I would guess that is because the out of the box experience is better.

WorldMaker 5y ago

I've not tried Vite yet. I've been happy enough with snowpack so far, and they seem so similar in approach I haven't heard a reason to switch other than yes it does seem to be the new PR "hotness". Looking at Vite's own comparison I don't see a strong reason to switch that would impact most of my projects: https://vitejs.dev/guide/comparisons.html#snowpack https://vitejs.dev/guide/comparisons.html#snowpack But also I don't use Vue and I don't trust CSS Modules yet [1] which is their other most impactful feature of Vite. ([1] It still seems like reliable Browser support for CSS Modules is still 5 years away at the current rate, if it ever gets accepted as a standard. I don't think there's any obvious current objections and few browsers outside the Chromium hegemony to even really object today, but it's still one of those web standards that smells to me pessimistically like "it's never going to work right cross-browser", and even if I were less pessimistic about it, I prefer not to use them because I think they bloat CSS and subvert the intent behind cascading. At that point I think you might as well just use CSS-in-JS and that doesn't have to wait on web standards that may never arrive.)