tree 13f4d8bd9fbd33d2231ad3849aafece0dc600e39
parent 8ea9fec379c61e7ee6cebabb18649d1f9e203fca
author David Ostrovsky <david@ostrovsky.org> 1605947420 +0100
committer Thomas Dräbing <thomas.draebing@sap.com> 1647514310 +0000

Bump rules_nodejs to version 3.0.0

Version 3.0.0 fixed some bugs and added new features: [1].

yarn_install and npm_install will now fail if the lockfile is
out-of-date, rather than update it. This assumes that the tooling to
manually update the lockfile is used.

yarn_install now passes --frozen_lockfile by default, but it can use
yarn_install(frozen_lockfile = False) to go back to the old behavior.

New @bazel/typescript module is stricter now and added third party
strictness checks to the typescript compiler.

The new check is flagging this code as invalid:

tools/node_tools/node_modules_licenses/installed-node-modules-map.ts:75:25 - error TS21231: [tsetse] type assert `JSON.parse() as SomeExplicitType` for type & optimization safety.
	See http://tsetse.info/must-type-assert-json-parse.
        const version = JSON.parse(fs.readFileSync(packageJsonFile, {encoding: 'utf-8'}))["version"];

Disable this check: must-type-assert-json-parse, as fixing it is
outside of the scope of this change.

[1] https://github.com/bazelbuild/rules_nodejs/releases/tag/3.0.0

Release-Notes: skip
Bug: Issue 15771
Change-Id: I6835e29a00080ca90b649663361e261ad6ef0f8b