This repository was archived by the owner on Oct 9, 2023. It is now read-only.
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.
What is the goal of this PR?
Our fork of
rules-nodejs
is ~600 commits behind the official upstream repo and it's time to switch to upstream rules so it's easier to keep up.What are the changes implemented in this PR?
nodejs_jest_test
tojasmine_node_test
it()
instead oftest()
in test definitionsexpect(obj).toHaveLength(len)
is not available in Jasmine, so we useexpect(obj.length).toBe(len)
. This corresponds to exact definition of what original function does.xit()
instead oftest.skip()
jasmine.DEFAULT_TIMEOUT_INTERVAL
instead ofjest.setTimeout
await expectAsync(promise).toBeRejected();
instead ofawait expect(promise).rejects.toThrowError();
yarn
to install dependencies instead ofnpm
:rules-nodejs
(see theirREADME
)grpc
failed to install withnpm_install
— planning to open an issue soonnode_modules
to.gitignore
—rules-nodejs
now install Node deps right into workspace