Re: [Buildroot] [PATCH 2/2] package/sass: new package

[Thomas Perale via buildroot <buildroot@buildroot.org>]

Hi Thomas, Alexis,

> I am not super clear on what sass exactly does/is. But some time ago,
> we dropped all JS libraries from Buildroot:
> 
>   https://lore.kernel.org/buildroot/20250829103340.158873-1-thomas.perale@mind.be/
> 
> But sass doesn't seem to be one of those static JS libraries I guess
> because it installs some executable host tool?

If I remember correctly node-sass is build using node-gyp so I can make sense
to have it in Buildroot because the node-sass version is closely related to the
node version present in Buildroot.

The question is how do you plan to use 'node-sass' once you have the executable.
Correct me if I'm wrong but I guess the goal here is to use it in another
Buildroot package that represent a "webapp" and you run 'node-sass'
in the build step of that package and then place the generate css in the
correct location ?

The correct way handle this (and minification) would probably be to use a
dedicated JavaScript bundler and configure it to use node-sass and setup
minification. This would probably yield smaller bundles and help handle
versioning correctly for your webapp.
This was also the thinking in dropping the JS libraries from Buildroot.

If you have a `package.json` for the webapp with the node-sass dependency. Can
you `npm install` the webapp dependencies using the buildroot 'npm'
host-package without errors ? If that's the case I would say that it is
probably a better solution.

Best regards,
PERALE Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot