Skip to content
Merged
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changeset/free-onions-guess.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
---
---
6 changes: 5 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,10 @@
"files": [
"dist"
],
"packageManager": "pnpm@9.15.9",
"packageManager": "pnpm@10.26.2",
"engines": {
"pnpm": "^10.26.2"
},
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added, but I think engines will cause a problem for Airnode. Is there a strong reason it's needed here?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm good point 👍. Seeing as this package.json gets published to NPM it probably doesn't make sense to set the "pnpm" version like this. I think lets remove it.

FYI it's mostly a sanity check for non-corepack users/contributors of a repo. E.g. if someone wants to contribute to the repo but isn't using a pnpm version that falls into this range, then pnpm install would fail.

"scripts": {
"build": "pnpm run clean && pnpm run compile",
"changeset": "changeset",
Expand All @@ -38,6 +41,7 @@
"@types/jest": "^30.0.0",
"@types/lodash": "^4.17.20",
"@types/node": "^20.19.24",
"eslint": "^8.57.1",
"husky": "^9.1.7",
"jest": "^30.2.0",
"prettier": "^3.6.2",
Expand Down
Loading