Why ignore nitrogen/generated folder?

[maitrungduc1410]

I see that if we choose Nitro modules, the nitrogen/generated folder is in gitignore. This means when user install our lib they'll need to run nitrogen to generate native bindings?

But in Nitro modules website they say:

You should push the files in ./nitrogen/generated/ to git, and make sure those files are part of your npm package. This way your library will always ship a working package as a whole (including generated interfaces), and the user does not need to do anything else than to install your package.

Why do we decide to not add nitrogen/generated to git?

Thanks for your time

[satya164]

That's what the prepare/prepack scripts are for - they automatically run when publishing a package. Generating the files with those scripts (which our templates do by default), makes sure you ship a working package and user doesn't need to do anything.

Committing generated code results in a noisy git diff, making it harder to review changes, unnecessary merge conflicts, an additional step to make sure that they are always up-to-date, etc. So, if you want to commit them, it depends on whether you're fine with these drawbacks, and if you get any specific benefit from committing them.