.gitignore not generated when init

[tlylt]

Please confirm that you have searched existing issues in the repo

Yes, I have searched the existing issues

Any related issues?

No response

Tell us about your environment

macOS 14

MarkBind version

5.2.0

Describe the bug and the steps to reproduce it

When running npx markbind-cli init, the .gitignore file is not generated. I tested on Windows 10 and it seems to work fine. May need someone to confirm using a mac machine.

Expected behavior

Should generate .gitignore as per https://markbind-master.netlify.app/userguide/gitignorefile

Anything else?

No response

[kaixin-hc]

Tested with MarkBind 5.2 on macOS 13.6

• When using the globally released version npm un -g markbind-cli, followed by npm i -g markbind-cli, followed by npx markbind-cli init, the .gitignore file is not produced
• When linked to this git version (cd packages/cli followed by npm link), the .gitignore file is produced.

Perhaps the difference lies there 🤔

[tlylt]

Perhaps the difference lies there 🤔

Seems like it could be. If you do the dev dependency method to install markbind, you can check the npm_modules folder for the files we ship. Not sure if I have the correct local, but it looks like at least for the markbind core i have, it doesn't contain the .gitignore file.

Maybe something to do with how we release markbind

[LamJiuFong]

Maybe because the .gitignore is not released as part of the package due to some restrictions of npm (they don't allow .gitignore to be part of a package). Hence the file will not be copied over when running markbind init

A common workaround is to rename the .gitignore to gitignore before publishing. Then as part of an init script, rename the gitignore file to .gitignore.
https://stackoverflow.com/questions/24976950/how-do-i-include-a-gitignore-file-as-part-of-my-npm-module

I have tried to publish my own package and the .gitignore file I created is indeed not published on npm. And it is also possible to copy a gitignore file to a .gitignore when doing init. I will work in this direction and try to resolve this issue.