OpenAPITools / OpenAPITools/openapi-generator
Hard snapshot paths in pkg executable nodejs-express-server generated application
Open
Nobody has claimed this yet.
Issue: Bug
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
When i (on a Windows machine) generated a nodejs-express-server application and do:
- add services//* controllers//* and node_modules/**/* in package.json (pkg assets)
- npm install
- pkg . -t node10-win-x64
- run the exe
I see errors about E:\snapshot (builded on a windows machine drive E:) :
Error: EEXIST: file already exists, mkdir 'E:\snapshot\appname\uploaded_files
More important: when i copy executable to a windows machine without E: drive i get:
Error: UNKNOWN: unknown error, chdir 'E:\snapshot\appname\api
openapi-generator version
4.3.1
5.0.0-beta
OpenAPI declaration file content or url
Generation Details
Steps to reproduce
Related issues/PRs
Suggest a fix
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the nodejs-express-server generation on Windows using the reported package.json assets, npm install, and pkg . -t node10-win-x64 steps. Start by inspecting the generated application's handling of uploaded_files and api paths; done means the executable runs without hard-coded E:\snapshot paths and also works on a machine without that drive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100