jol/migrate to eslint v9 and node v18 #230
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
npm workspaces doesn't detect dependency topology when building multiple workspaces. I don't know when, and I don't care to debug it. - npm/cli#4139 - npm/cli#3034
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
chore(deps): update dependency eslint to v9
fix(lint): migrate eslint config in infra package
feat: migrate config to eslint v9
chore: lint fix
chore: migrate jest configs to esm
feat: upgrade to nodejs 18
build: specify build order (see comment)
npm workspaces doesn't detect dependency topology when building multiple
workspaces. I don't know when it broke, and I don't care to debug it.