Both lightningcss and esbuild publish prebuilt binaries as individual npm packages which are declared as optionalDependencies. This technique allows package managers to skip downloading the binaries for irrelevant architectures/platforms.
It would be great if @parcel/watcher used the same approach. The current method is a hurdle for projects seeking to minimize the size/cost of dependencies.
I think a sensible starting place might be the GitHub Actions workflows for lightningcss or esbuild. Happy to help contribute
Both lightningcss and esbuild publish prebuilt binaries as individual npm packages which are declared as
optionalDependencies
. This technique allows package managers to skip downloading the binaries for irrelevant architectures/platforms.It would be great if @parcel/watcher used the same approach. The current method is a hurdle for projects seeking to minimize the size/cost of dependencies.
I think a sensible starting place might be the GitHub Actions workflows for lightningcss or esbuild. Happy to help contribute
Related: