3 ms·
> Currently, migrating to Turbopack from Webpack is not yet possible Bummer! Do I need a turbopack.config.js? I've still got my package.json, tsconfig.json, .
by cantSpellSober 4y ago
> Currently, migrating to Turbopack from Webpack is not yet possible
Bummer! Do I need a turbopack.config.js?
I've still got my package.json, tsconfig.json, .env, and postcss.config.js apparently.
> [Turbopack cannot currently be configured with plugins. We plan to make Turbopack extensible, likely with an altered API]
Will I be able to use my current plugins? Where does config for these plugins live?
> [SCSS and LESS] don't currently work out-of-the-box with Turbopack
Keep it this way! LESS has been dead and SCSS dying. Focus on CSS Modules please!
- jacquesc 4y agoWhat's wrong with SCSS modules? It has a lot of really useful functionality that frontend developers like me love.
- cantSpellSober 4y agoThey still require a preprocessor. Let's push to get that stuff into CSS! Worst case run `npm install sass`.
- munbun 4y ago`node-sass` was the fastest solution (node bindings to a C++ library) was deprecated a few years back. `sass` (dart-sass) is the current iteration but it’s an order of magnitude slower for larger projects with many small scss module files. I’ve seen it add +10 to 30 seconds. `sass-embedded` will be the next iteration for dart-sass but in its current form still suffers from similar issues. I believe using postcss for nesting support + css variables is a better alternative, considering that css will likely get native nesting support in a few years. https://www.w3.org/TR/css-nesting-1/ https://www.w3.org/TR/css-nesting-1/