Date: Wed, 30 Oct 2019 13:26:53 -0700 From: Yuri <yuri@rawbw.com> To: Willem Jan Withagen <wjw@digiware.nl>, "ports@freebsd.org" <ports@freebsd.org> Subject: Re: packaging a port that uses npm during build. Message-ID: <c7b17e66-e5b1-4794-80c0-5c01e16bd648@rawbw.com> In-Reply-To: <4566de44-a796-d449-242b-657420266a20@digiware.nl> References: <ed00bd7d-c13c-f7ec-1fbb-48b97f242a6c@digiware.nl> <1455167b-62ca-0601-ff27-e86fa54baecf@rawbw.com> <4566de44-a796-d449-242b-657420266a20@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-10-30 13:16, Willem Jan Withagen wrote: > > > But my project includes about a npm 62 toplevel packages. :-( > and many more getting installed as extra dependancies. > So that is not really an option. 'npm install -l' does the basic local installation, it has a ton of options that allow it to install extra/optional dependencies. So I am pretty sure that this approach can be used with most npm-based projects, except when they attempt to build some native libs and fail for some obscure reasons. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c7b17e66-e5b1-4794-80c0-5c01e16bd648>