Arch Linux User Repository

I'm going to do a best-effort to update this regularly considering the frequency of upstream updates. If someone can do better, let me know, but for now I'll just keep updating when I have a chance. Better than nothing, I think ;-)

The upstream release cadence is so nuts because they've automated things like javascript dependency updates. I don't think it necessary to hit every one of those since they aren't really updated code releases, if you know what I mean.

The latest release has some node warnings on the command line. I don't think this affects functionality, but I'm not sure if people want me to package this?

(node:1136716) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
wasm streaming compile failed: TypeError: Failed to parse URL from /usr/lib/node_modules/netlify-cli/node_modules/netlify-redirector/lib/redirects.wasm
falling back to ArrayBuffer instantiation

I'm going to do a best-effort to update this regularly considering the frequency of upstream updates. If someone can do better, let me know, but for now I'll just keep updating when I have a chance. Better than nothing, I think ;-)

The upstream release cadence is so nuts because they've automated things like javascript dependency updates. I don't think it necessary to hit every one of those since they aren't really updated code releases, if you know what I mean.

Due to the crazy release cadence of this package (10 releases in the past week), I've been having trouble keeping up. If anyone is interested in being a co-maintainer (or taking over maintenance entirely), please let me know. Otherwise, I'll continue to release updates when I can.

I have considered completely automating the update process, but I think there is value in reviewing upstream releases before pushing them, especially given some of the recent prominent supply-chain attacks.

@mutantmonkey after some research I came to the conclusion that adding dependencies to a nodejs PKGBUILD is not a good idea.

Therefore forget everything I wrote, since it is just wrong.

@andreafeletto I'm not too familiar with how npm works, but currently these dependencies are getting bundled into this package under node_modules. Would installing these packages before building automatically change this behavior, or am I going to have to rework the build process?

I just packaged nodejs-boxen (and its entire dependency tree) which is a dependency of netlify. Could you please add it as a dependency?

Part of the dependency tree of boxen is also a dependency of netlify:

• nodejs-ansi-styles

• nodejs-chalk

Could you add these too?

Great, the install is much faster, thanks!

I'm not 100% sure this is the right place to ask, but it seems like this package is having strip run on install, which is possibly not necessary? It means the install time is a couple of minutes longer. Would you consider disabling it please?