Il Lun 6 Giu 2022, 13:16 Andrew Ammerlaan <andrewammerl...@gentoo.org> ha scritto:
> Hi Chris, > > I think @Alessandro (CC) has already done some work on this over at [1]. > I'm not sure what the status of it is though. Maybe you two can discuss > this together to avoid doing double work. > > Best regards, > Andrew > > [1] https://github.com/Alessandro-Barbieri/node-overlay > > On 05/06/2022 07:47, Chris Pritchard wrote: > > Hello, > > > > Would there be any interest in a yarn / NPM eclass that supports offline > > installs. For a personal overlay I’ve got a working yarn.eclass > > ( > https://github.com/chriscpritchard/overseerr-overlay/blob/main/eclass/yarn.eclass > > < > https://github.com/chriscpritchard/overseerr-overlay/blob/main/eclass/yarn.eclass>) > > > and I’ve been able to make a version that supports npm from > > NPM-Shrinkwrap or npm-lock.json files (this is still being tested). > > > > If there is an interest, would anyone be willing to support me in having > > an eclass added to the tree? > > > > Thanks, > > > > Chris > > I'm interested in an eclass that doesn't bundle everything together. Also I'm interested in anyone that can share the package maintainership (in guru first). I've already tried 3 approaches: 1) one package per dependency. The npm eclass is working fine for now, you can unbundle packages that depend on system libs (like sqlite), the major issue I've found is in the circular dependencies of the rollup package. 2) bundle everything. This approach doesn't always work. Some packages fail to build dependencies written in C and you can't unbundle them. 3) package every runtime dependency and bundle build time dependencies. Since rollup is a build time dep, I've tried to bundle every build time dep but this require to create a custom stuff and host it somewhere.
