This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
build: enable npm package publication from master branch #878
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.
PR checklist
Overview of change:
beta
tags on npm 😄tslint.json
now will be created fromlegacy.json
(therefore rules that were added after6.0
were removed from it)Is there anything you'd like reviewers to focus on?
After applying this PR there should be only three files inside package that differ from latest version:
legacy.json
- removedreact-a11y-accessible-headings
andvoid-zero
rules because they were added in6.1
package.json
- removedscripts
to unblock publishing fromdist/build
tslint.json
- will produce big diff because of different formatting and rules sort. Summary of changes:no-reserved-keywords
(recommended rulevariable-name
was already enabled)no-function-constructor-with-string-args
,no-increment-decrement
, andno-unnecessary-bind
rules and enabled corresponding recommended rules from TSLint