Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 torequire
it.Release: Just run
npm run release
from the cli and the script bumps bothbower/npm
versions, check-outs newrelease
branch, builds the library, creates proper.gitignore
, publishes the new release branch and also the new git tag. If the maintainer uncommentsnpm 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.