Skip to content
This repository was archived by the owner on Oct 16, 2025. It is now read-only.

Update dev dependencies#96

Merged
mcmire merged 2 commits into
mainfrom
upgrade-deps
Apr 12, 2022
Merged

Update dev dependencies#96
mcmire merged 2 commits into
mainfrom
upgrade-deps

Conversation

@mcmire

@mcmire mcmire commented Apr 11, 2022

Copy link
Copy Markdown
Contributor
  • Use latest version of @metamask/eslint-config; add accompanying
    packages
  • Add .prettierrc from module template, as we now require it
  • Fix linting issues caused by these changes
  • Bump TypeScript to 4.4.x (no accompanying changes needed)
  • Bump tape from ^4.9.0 to ^5.5.3
    • Remove redundant t.end() from async tests, which are causing
      errors. According to the tape README:

      If cb returns a Promise, it will be implicitly awaited. If that
      promise rejects, the test will be failed; if it fulfills, the test
      will end. Explicitly calling t.end() while also returning a
      Promise that fulfills is an error.

@mcmire mcmire requested a review from a team as a code owner April 11, 2022 18:03
* Use latest version of `@metamask/eslint-config`; add accompanying
  packages
* Add `.prettierrc` from module template, as we now require it
* Fix linting issues caused by these changes
* Bump TypeScript to 4.4.x (no accompanying changes needed)
* Bump `tape` from ^4.9.0 to ^5.5.3
  * Remove redundant `t.end()` from async tests, which are causing
    errors. According to the `tape` README:
    > If `cb` returns a Promise, it will be implicitly awaited. If that
    > promise rejects, the test will be failed; if it fulfills, the test
    > will end. Explicitly calling `t.end()` while also returning a
    > Promise that fulfills is an error.
Comment thread .eslintrc.js Outdated
],
files: ['*.js'],
parserOptions: {
sourceType: 'script',

@Gudahtt Gudahtt Apr 12, 2022

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we need this? Our ESLint Node.js config has this comment:

// The recommended Node.js plugin config sets the correct sourceType per the
// type field of the local package.json file, so we don't set that here.

That implies to me that we don't need to set this explicitly.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

You're right. Good call. Removed accordingly in 6abe742.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This was probably taken from the module template? Looks like the same mistake is made there as well

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yup! Okay, I'll make a change there as well.

Comment thread .eslintrc.js

@Gudahtt Gudahtt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!

@mcmire mcmire merged commit e7c075a into main Apr 12, 2022
@mcmire mcmire deleted the upgrade-deps branch April 12, 2022 21:24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants