We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
dist/bundle.js was always there in the repo, but then we added release automation and it anyway is always available, fresh and nice on the release level, example: https://github.com/asyncapi/parser-js/releases/tag/v1.14.1
dist/bundle.js
In other words: bundle.js is already available on a release level + npm package.
bundle.js
Having it in the repo only causes confusion and continuous issues:
What do you think?
cc @jonaslagoni @fmvilas @magicmatatjahu
We need to:
.gitignore
package.json
The text was updated successfully, but these errors were encountered:
Let's remove it.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Reason/Context
dist/bundle.js
was always there in the repo, but then we added release automation and it anyway is always available, fresh and nice on the release level, example: https://github.com/asyncapi/parser-js/releases/tag/v1.14.1In other words:
bundle.js
is already available on a release level + npm package.Having it in the repo only causes confusion and continuous issues:
What do you think?
cc @jonaslagoni @fmvilas @magicmatatjahu
Description
We need to:
bundle.js
from this repobundle.js
is also available on a release levelbundle.js
to.gitignore
package.json
to make surebundle.js
is an exception and that even though it is ignored, it should be pushed to npmThe text was updated successfully, but these errors were encountered: