New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC .projenrc.ts support #14
Comments
|
Yes, why not? |
|
I am having seconds thoughts here. Let's keep it in the backlog for now and see how far we can get with JavaScript. |
|
This will also require |
|
Maybe |
|
That would mean that every time you run projen ts-node will be executed or it has to be installed globally (which means that This is related to perhaps adding support for other languages. Would be nice to be able to also author projenrc in python for example, which will also have some ambient prerequisites. I am open to doing that: we can auto-discover the .projenrc file type based on its extension and then require the user to have the "runtime" pre-installed in their system. |
|
There's also https://github.com/antfu/esno, which uses Maybe a file like |
|
|
|
Exactly, it just executes the code. Maybe that's not what you want in this scenario. |
|
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. |
|
Projenrc in typescript is now supported via: projen new typescript --projenrc-ts |
For more complex projects, specially with the monorepo support, wouldn't it be interesting to:
npx projen init typescript --typesThen generate a .projenrc.ts file instead of the .js and incorporate a check on the cli to compile on the fly if .ts file is there?
The text was updated successfully, but these errors were encountered: