Nx Release support for projects without package.json files #23389
Replies: 5 comments
-
Could you please provide a reproduction of this issue so we can see more about what you are trying to do? If you want to publish your node api to NPM, then you'll need a But it seems more like you want to deploy your Node API to be hosted somewhere. |
Beta Was this translation helpful? Give feedback.
-
Yes indeed! I need to deploy my application. It needs to be hosted on a VPS. I've found it to be a little tricky! Firstly I can't release it because it's not a js library, secondly I needed to manually create a package.json file inside the src, then the build target will pick it and add the dependencies manually. In this way the application can be deployed |
Beta Was this translation helpful? Give feedback.
-
I ran into the same issue when using Nx in a polyglot repo. I posted in discord but had no answers. Let me copy here the core of the question:
Regarding 2: have you thought of decoupling the following? I guess I could write a generator myself and pass it in the nx.json in Is there I way I can use your code without rewriting all the version calculation myself? Thank you! |
Beta Was this translation helpful? Give feedback.
-
Hi @ctrlmaniac and @mpsanchis, the release version generator is currently designed to manage versions of npm packages, which require a While it's currently possible to replace the version generator, we recognize that it's difficult because of the sheer amount of functionality in the existing We appreciate your input. I'm going to convert this to a feature so that it can be prioritized accordingly. |
Beta Was this translation helpful? Give feedback.
-
Hi @fahslaj In case you guys discuss this internally:
is not enough in my opinion. In a polyglot release group, say with JS and Rust, the JS applications will be versioned with If you are open to re-considering the way Maybe I'm the only one considering polyglot release groups... In any case, I hope these ideas were useful to start a conversation in Nx. 🚀 |
Beta Was this translation helpful? Give feedback.
-
Current Behavior
nx release fails when package.json is missing in projects
Expected Behavior
nx release to run even without a package.json or to use the package.json inside the dist folder
GitHub Repo
No response
Steps to Reproduce
nx g @nx/node:app api
nx release --dry-run
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
Beta Was this translation helpful? Give feedback.
All reactions