Adding crypto makes nodelibs a 10 package install, which can easily be seen as overkill for a simple app, and detracts from the configuration simplicity for model cases, which is important to keep.
Ideally we could detect specific node core libs, and only include them when they are used. Then instead of having a single nodelibs repo, we download the nodelibs repos we need as we need them.
The reason this isn't currently supported is because dependencies are returned from getPackageConfig, which is before download completion, and download dependencies are ignored.
The addition would be to allow the build function to return further dependencies. This is the simplest fix and most sensible one.
Adding crypto makes nodelibs a 10 package install, which can easily be seen as overkill for a simple app, and detracts from the configuration simplicity for model cases, which is important to keep.
Ideally we could detect specific node core libs, and only include them when they are used. Then instead of having a single nodelibs repo, we download the nodelibs repos we need as we need them.
The reason this isn't currently supported is because dependencies are returned from getPackageConfig, which is before download completion, and download dependencies are ignored.
The addition would be to allow the build function to return further dependencies. This is the simplest fix and most sensible one.