Fix compile errors in tsbuildWatchMode.ts #115
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.
Included changes:
Update minimum Yarn version from 1.3.2 to 1.10.1
Yarn 1.10 added the integrity field to the lockfile, making newer Yarn users
have their lockfile changed a lot if they run
yarn
. This commit updates therequired Yarn version to be at least 1.10.1 and changes Travis & Jenkins to use
Yarn 1.10.1
Change the package.json's engines grunt field to grunt-cli
The grunt field suggested it's the grunt package version we're checking while
we check the grunt-cli version instead.
Stop separating Yarn script arguments from script names via " -- "
The " -- " separator is necessary in npm but not in Yarn. In fact, it's
deprecated in Yarn and some future version is supposed to start passing this
parameter directly to the scripts which may break them.
Don't install grunt-cli globally during the build
It's enough to use
yarn grunt
instead ofgrunt
and the global grunt-cliinstallation is no longer needed.
Use
yarn grunt
instead ofyarn run grunt
The former form is shorter.
Don't define the
grunt
Yarn scriptAs opposed to npm,
yarn binName
invokes a binary namedbinName
exposedby the respective package so the
grant
Yarn script is no longer needed.Allow Node versions newer than 8; bump the minimum
Closes angular#16714
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements
Other information: