Skip to content
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

+ Build and Publish #405

Closed
wants to merge 1 commit into from
Closed

+ Build and Publish #405

wants to merge 1 commit into from

Conversation

tenbits
Copy link

@tenbits tenbits commented Dec 1, 2014

Hello Team,

there is still no npm package, components and plugins are not ready to use in node env., and the bower package is from the 3rd part source.
I'm proposing here automatically build and release the prism.

Build: For the node environment, factory wrapper is used for each component and plugin, so it is then possible to require it.
Release: Just run npm run release from the cli and the script bumps both bower/npm versions, check-outs new release branch, builds the library, creates proper .gitignore, publishes the new release branch and also the new git tag. If the maintainer uncomments npm publish line this will also publish the package. Bower's package updates after the new tag is created (but we should ask the current bower maintainer to update the repo url).

There is how release branch looks then: prism/release

Should you have any questions please give me a note, Alex.

@tenbits tenbits force-pushed the builder branch 4 times, most recently from 9230a1b to b052616 Compare December 3, 2014 21:14
@Mrman
Copy link

Mrman commented Feb 17, 2015

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants