Refactoring for janus.js release on npm #3220
Merged
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.
Since we have taken the ownership of the janus-gateway package on npm, this PR refactors the project for the release of
janus.js
in the npm public registry.Potentially breaking changes
package.json
in the project root has been removednpm/dist
./npm/package-lock.json
has been added (deps versions updated)./npm/package.json
has been refactoredHow janus.js packages will be published
We have added a
prerelease
script to./npm/package.json
that generates an ES version ofjanus.js
throughrollup
under./npm/dist/janus.es.js
and copyjanus.js
under./npm/src/janus.js
So basically the publishing cycle will be the following (remove
--dry-run
)The package published on npm will have the following contents:
Feedbacks are very welcome, in particular about the project structure we defined and how we think to manage the release cycle.