Is dukat ready for production environment? Looks there're many problems on the output definitions. A...

# javascript

[iseki]

Is dukat ready for production environment? Looks there're many problems on the output definitions. And... I don't know how to resolve them manually.

[turansky]

Which declarations do you need?

[iseki]

Just like js-joda and Deno lib

[iseki]

I must edit every file manually and if I regenerate it for new deps, something which are shared will be overwrite...(like es2015 or dom.lib

[turansky]

Effective scheme:
1. Generate via dukat
2. Fix compilation
3. Add package (jsjoda for example)
4. Save in separate subproject
Examples

[Ilya Goncharov [JB]]

There is task generateExternals which produce externals for you into separate folder. It is explicit task, so it is not run during build. And you can copy resulta of this task to appropriate place

[iseki]

But the generated definitely can't be compiled. If I use the task how do I fix the file?

[iseki]

Thank you for your reply.

[Vampire]

Another way is to programmatically fix the problems after generation: https://github.com/Vampire/setup-wsl/blob/master/buildSrc/src/main/kotlin/net/kautler/node.gradle.kts#L130