You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The most popular way according to GitHub stars is to copy & paste one from https://github.com/github/gitignore/blob/master/Node.gitignore . There is even a vscode plugin for that, that does this (I'm using it myself quite heavily). It ignores dist/ by default.
I know we went a bit back and forth on naming it dist/ vs .dist/ but the former arguable removes a friction point for users. Let's not repeat the same mistake in microbundle of requiring users to extend their .gitignore.
The text was updated successfully, but these errors were encountered:
The trick here is that currently dist/ is used for production output, whereas .dist is used for static files generated during development. Because one is unbundled and the other bundled, they're a very different set of files.
Looking at the gitignore you linked, maybe we could use .cache as the development output directory? That's essentially what the disk files are used as, they're never served directly.
The most popular way according to GitHub stars is to copy & paste one from https://github.com/github/gitignore/blob/master/Node.gitignore . There is even a vscode plugin for that, that does this (I'm using it myself quite heavily). It ignores
dist/
by default.I know we went a bit back and forth on naming it
dist/
vs.dist/
but the former arguable removes a friction point for users. Let's not repeat the same mistake in microbundle of requiring users to extend their.gitignore
.The text was updated successfully, but these errors were encountered: