-
Notifications
You must be signed in to change notification settings - Fork 27
Publish to npm for easier consumption #36
New issue
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
Comments
Do you have any plans for this? Having some king of alpha release publish would greatly simplify the steps we need to take in our build/deploy process. |
At current to globally install the package and run it we have to do the following:
Ideally dist should be published to NPM having been built in the CI as at the moment we need to install dev dependencies to run the build and get a working copy. Is the plan to introduce versioning? This would make it much easier to trigger an automated |
Have a TODO in the very near future to get a publishing process setup for the team that will be helping to take over maintenance of Baler :). If you don't see anything by this time next week please bug me about it |
( ͡° ͜ʖ ͡°) |
Ugh, I'm the worst 😆 Really trying to carve time out for this - just under some tight time constraints lately |
Hi @DrewML, Is the plan still to publish this to NPM? If so, any idea when? Many Thanks |
No description provided.
The text was updated successfully, but these errors were encountered: