Hi Stefan,
On Oct 24, 2019, at 1:22 PM, Stefan Herbrechtsmeier ste...@herbrechtsmeier.net
wrote:
> Am 22.10.19 um 11:03 schrieb Jean-Marie LEMETAYER:
>> Many issues were related to npm dependencies badly handled: package
>> names, installation directories, ... In fact npm is using an install
>> a
Hi Jean-Marie,
Am 22.10.19 um 11:03 schrieb Jean-Marie LEMETAYER:
Many issues were related to npm dependencies badly handled: package
names, installation directories, ... In fact npm is using an install
algorithm [1] which is hard to reproduce / anticipate.
Why do you think it is hard to repro
On Oct 22, 2019, at 1:35 PM, Alexander Kanavin alex.kana...@gmail.com wrote:
> On Tue, 22 Oct 2019 at 11:12, Jean-Marie LEMETAYER <
> jean-marie.lemeta...@savoirfairelinux.com> wrote:
>
>> The simplest solution is to let npm do its job. Assuming the fetcher
>> only get the sources of the package,
On Tue, 22 Oct 2019 at 11:12, Jean-Marie LEMETAYER <
jean-marie.lemeta...@savoirfairelinux.com> wrote:
> The simplest solution is to let npm do its job. Assuming the fetcher
> only get the sources of the package, the class will now run
> 'npm install' to create a build directory. The build directo
Many issues were related to npm dependencies badly handled: package
names, installation directories, ... In fact npm is using an install
algorithm [1] which is hard to reproduce / anticipate. Moreover some
npm packages use scopes [2] which adds more complexity.
The simplest solution is to let npm
