search

trumbitta / nx-trumbitta

💡An attempt to start collecting all of my Nx-related Open Source work in a mono-repo.
MIT License
47 stars 11 forks source link

Allow specifying custom outputPath #58

Open youngchen7 opened 2 years ago

youngchen7 commented 2 years ago

I think it would be beneficial to be able to specify an outputPath - currently if I'm understanding this correctly the outputPath is always set to the current library directory.

It would be nice to take advantage of NX's caching mechanisms, as well as avoid committing autogenerated code.

Or would it be considered bad practice to have raw typescript code in the dist/ directory?

(Let me know if I'm totally off-base here, I've only been playing with NX for about a week).

Teddarific commented 2 years ago

This seems really useful, big plus one!

trumbitta commented 2 years ago

I'm not sure about this 🤔

On one hand, why not? Seems a pretty common option to have in tools like this one. On the other hand, it kind of defies the whole approach of this plugin: having one lib for the spec file, and one lib for the autogenerated code. And you could use a .gitignore to avoid committing the code if you don't need to (I do 😆)