Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add node@19 to integration tests + use it in CI #3848

Merged
merged 1 commit into from
Feb 17, 2023

Conversation

IvanGoncharov
Copy link
Member

Motivation: to run it as part of integration tests and also use it in CI

@netlify
Copy link

netlify bot commented Feb 14, 2023

Deploy Preview for compassionate-pike-271cb3 ready!

Name Link
🔨 Latest commit ebaa3f1
🔍 Latest deploy log https://app.netlify.com/sites/compassionate-pike-271cb3/deploys/63eff7b4c10ac4000849ba7c
😎 Deploy Preview https://deploy-preview-3848--compassionate-pike-271cb3.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@github-actions
Copy link

Hi @IvanGoncharov, I'm @github-actions bot happy to help you with this PR 👋

Supported commands

Please post this commands in separate comments and only one per comment:

  • @github-actions run-benchmark - Run benchmark comparing base and merge commits for this PR
  • @github-actions publish-pr-on-npm - Build package from this PR and publish it on NPM

IvanGoncharov added a commit to IvanGoncharov/graphql-js that referenced this pull request Feb 16, 2023
Motivation: We need to have a way to have internal ESLint rules.
ESLint allows you to import rules in two ways:
1. As an npm package, it is problematic for internal rules since we don't want to publish it on NPM. So in the past, we used NPM-specific workarounds to treat a directory as a package.
2. `--rulesdir` CLI option, the problem with it is deprecated.

ESLint team is planning to deprecate the current config format and switch to:
https://eslint.org/docs/latest/use/configure/configuration-files-new
This format forces you to import plugins manually, and it entirely resolves our problem with internal rules. But it requires that all plugins that we use to support this format.

I propose to temporarily switch to `--rulesdir` and start working on changing to the new format since the entire config format will be deprecated anyway.
This switch will unblock support for node@19 in CI and local development and unblock graphql#3848.
Motivation: to run it as part of integration tests and also use it in CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant