<div dir="ltr"><div dir="ltr">On Thu, 24 Oct 2019 at 14:02, Stefan Herbrechtsmeier <<a href="mailto:stefan@herbrechtsmeier.net">stefan@herbrechtsmeier.net</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
@Richard: What is your opinion about the per recipe dependency? <br>
Typically OE use one recipe per project. The NPM based solution handle a <br>
project and all dependencies via one recipe.<br></blockquote><div><br></div><div>I don't think it's at all realistic to stick to the 'one recipe per component' in node.js world. A typical 'npm install' can pull down hundreds, or over a thousand dependencies, it's not feasible to have a recipe for each.</div><div><br></div><div>I very much welcome a solution that uses 'npm install' in a way that preserves offline builds, and integrity/reproducibility of downloads. License management should be also handled by npm, and if it isn't, then we need to work with the upstream to address it.<br></div><div></div><div><br></div><div>Alex<br></div></div></div>