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 engines to package.json #442

Merged
merged 3 commits into from
Dec 25, 2023

Conversation

toasted-nutbread
Copy link

Should help avoid issues such as #434 (comment).

@toasted-nutbread toasted-nutbread requested a review from a team as a code owner December 24, 2023 22:17
Copy link

github-actions bot commented Dec 24, 2023

✔️ No visual differences introduced by this PR.

View Playwright Report (note: open the "playwright-report" artifact)

Copy link
Collaborator

@djahandarie djahandarie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had been using .node-version file to inform CI about the appropriate node version, but maybe we could get rid of that, and pass 'package.json' into the setup-node action node-version-file parameter now that we have this? (See https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#node-version-file)

@djahandarie djahandarie added this pull request to the merge queue Dec 25, 2023
Merged via the queue into themoeway:master with commit 8999442 Dec 25, 2023
5 checks passed
@djahandarie djahandarie added the kind/meta The issue or PR is meta label Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/meta The issue or PR is meta
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants