3 ms·
Your (potential) problems will come at the installing node/packages (that might use C extensions or whatever) level, not developing on top of it. Or just tooli
by OJFord 4y ago
Your (potential) problems will come at the installing node/packages (that might use C extensions or whatever) level, not developing on top of it.
Or just tooling issues like BSD vs. GNU versions, Homebrew installing things differently (e.g. using the more logical 'openapi-generator' vs. 'openapi-generator-cli' used by upstream and respected by at least apt, apk, and pacman).
- nicoburns 4y agoDo you use Python by any chance? Node.js native modules typically bundle the native code as part of the module, and don’t depend on externally installed tools. I’ve never used OpenAPI generator, but that looks true of this npm package too https://www.npmjs.com/package/@openapitools/openapi-generator-cli https://www.npmjs.com/package/@openapitools/openapi-generato... (read me mentions the tool is downloaded and installed on first run). I’ve had issues where modules didn’t run when upgrading OS versions (either macOS or Linux - but usually macOS), but we run prod on LTS versions of Ubuntu so that doesn’t happen very frequently, gets caught by our staging server, and is usually a case of simply upgrading libraries to newer versions.
- OJFord 4y agoI use both, and have had such issues with both. I suppose using busybox as your base image will most readily highlight any missing library issues if you fancy it. (If I remember in the morning I think I can quite quickly find whatever it was that was last a problem - it was definitely an npm not a pip install when last I encountered it.)