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

maintenance #602

Merged
merged 4 commits into from
Jul 2, 2021
Merged

maintenance #602

merged 4 commits into from
Jul 2, 2021

Conversation

mightyiam
Copy link
Owner

  • test(deps): log dep in peer dep inclusion test
  • fix(deps): expand eslint-plugin-promise peerDep to equal upstream
  • fix(deps): sort peer deps
  • chore(deps): update some dev deps

t.is(ourDep, standardDep)
t.is(ourDep, standardDep, name)
Copy link
Owner Author

Choose a reason for hiding this comment

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

This shows us which peer dep is not in alignment with upstream.

package.json Outdated
"eslint-plugin-promise": "^4.2.1",
"eslint-plugin-promise": "^4.2.1 || ^5.0.0",
Copy link
Owner Author

Choose a reason for hiding this comment

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

This aligns with upstream.

package.json Outdated
Comment on lines 62 to 67
"@typescript-eslint/eslint-plugin": "^4.0.1",
"eslint": "^7.12.1",
"eslint-plugin-import": "^2.22.1",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-promise": "^4.2.1 || ^5.0.0",
"typescript": "^3.9",
"@typescript-eslint/eslint-plugin": "^4.0.1"
"typescript": "^3.9"
Copy link
Owner Author

Choose a reason for hiding this comment

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

I noticed that npm sorted this for me when I used npm install so I gave the sorting its own commit.

"@types/node": "14.17.3",
"@types/node": "15.14.0",
Copy link
Owner Author

Choose a reason for hiding this comment

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

I'm not sure how versioning for this works but as long as type checking works we're good, I guess.

"eslint-plugin-import": "2.23.4",
"eslint-plugin-node": "11.1.0",
"eslint-plugin-promise": "4.3.1",
"husky": "6.0.0",
"eslint-plugin-promise": "5.1.0",
Copy link
Owner Author

Choose a reason for hiding this comment

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

Changelog isn't helpful in figuring out what the breaking change is. But we're not using it directly, buy via upstream, so OK I guess.

"eslint-plugin-promise": "4.3.1",
"husky": "6.0.0",
"eslint-plugin-promise": "5.1.0",
"husky": "7.0.0",
Copy link
Owner Author

Choose a reason for hiding this comment

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

Breaking change is merely dropping unsupported Node.js version.

@mightyiam mightyiam marked this pull request as ready for review July 2, 2021 09:07
@mightyiam mightyiam merged commit 06a72d4 into master Jul 2, 2021
@mightyiam mightyiam deleted the maintenance branch July 2, 2021 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant