|
|
|
|
|
by jessaustin
2558 days ago
|
|
I haven't used Bootstrap in a while, but all I was saying above is that it rebuilds itself with a simple "npm run dist", which under the covers is a call to node-sass. That compiles sass files, but it's still not what I consider a build tool. (Attempting to override bootstrap with a css file is DOING IT WRONG.) For build tools, people used to use Grunt and Gulp. Now they use Webpack. Parcel is better than any of those, because does the right thing automatically. That could include calling node-sass, if you want. |
|
Parcel does seem nice, because it does do a lot of things automatically. But I'm not sure that can always be "the right thing". For example it seems a bit surprising that plain js will always be compiled, to support ie11, while typescript will not.
Neither option is "always the right thing".
And as far as I could figure out, there's no easy way to target deploying to separate cdns?
Not trying to move the goal posts here, it's just that some configuration is to expected in the complex reality of the modern web stack.
And a benefit of npm is that that'll pretty much always be part of the stack anyway.
Did come across this, which (if it isn't outdated) fills in some information that wasn't obvious from the official documentation:
https://golb.hplar.ch/2018/01/Bundling-web-applications-with...