refactor!: Synchronize dev toolchain with module template and core monorepo (#351)

Synchronizes package meta-files with
[MetaMask/metamask-module-template](https://github.com/MetaMask/metamask-module-template)
and [MetaMask/core](https://github.com/MetaMask/core). Changes exclude
source code and other published files with the following exceptions:
- `package.json`, most notably its `exports` field
  - This is due to adding fields expected by our Yarn constraints and
migrating to `ts-bridge` for builds.
- Published files are split into `.cjs` and `.mjs` trees per `ts-bridge`

In detail (all changes per module template unless otherwise specified):
- Use `ts-bridge`
- Bump `eslint`, `prettier`, and related dependencies
- Add `eslint.config.mjs`
  - Preserve previous lint configuration to the greatest extent possible
  - Some changes are made to test files
- `index.ts` and `PollingBlockTracker.ts` received some non-behavioral,
type-related lint modifications
- Add and use `@arethetypeswrong/cli`
- Add and use `typedoc`
- Update `.yarnrc.yml` and add `yarn.config.cjs`
- Update `package.json`
- Bump `typescript` from `4.x` to `~5.2.2`
- Downgrade `jest` and related dependencies from `^29` to `^27`
- Update `tsconfig` files per `ts-bridge` conventions
- Lint all files per updated config
  - Set the following rules to `warn`:
- `@typescript-eslint/prefer-nullish-coalescing`, to avoid behavioral
changes
- `@typescript-eslint/explicit-function-return-type`, because too many
violations to fix right now

Work intentionally avoided in this PR:
- Update `package.json#engines`
- Migrate to `vitest`

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> <sup>[Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) is
generating a summary for commit
58e0693. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: rekmarks

.depcheckrc.json

@@ -0,0 +1,22 @@
+{
+  "ignores": [
+    "@arethetypeswrong/cli",
+    "@lavamoat/allow-scripts",
+    "@lavamoat/preinstall-always-fail",
+    "@metamask/auto-changelog",
+    "@metamask/eslint-config",
+    "@metamask/eslint-config-*",
+    "@types/*",
+    "@typescript-eslint/utils",
+    "@vitest/coverage-istanbul",
+    "@vitest/eslint-plugin",
+    "@yarnpkg/types",
+    "eslint-config-*",
+    "eslint-import-resolver-typescript",
+    "eslint-plugin-*",
+    "prettier-plugin-packagejson",
+    "ts-node",
+    "typedoc",
+    "typescript-eslint"
+  ]
+}

.eslintrc.js

@@ -1,3 +1,8 @@
 * text=auto
 
 yarn.lock linguist-generated=false
+
+# yarn v3
+# See: https://yarnpkg.com/getting-started/qa#which-files-should-be-gitignored
+/.yarn/releases/** binary
+/.yarn/plugins/** binary

.gitattributes

@@ -0,0 +1,11 @@
+<!--
+Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes:
+
+* What is the current state of things and why does it need to change?
+* What is the solution your changes offer and how does it work?
+
+Are there any issues or other links reviewers should consult to understand this pull request better? For instance:
+
+* Fixes #12345
+* See: #67890
+-->

.github/pull_request_template.md

@@ -1,6 +1,7 @@
 .DS_Store
 dist/
 coverage/
+docs/
 
 # Logs
 logs

.gitignore

@@ -1,8 +1,11 @@
 // All of these are defaults except singleQuote, but we specify them
 // for explicitness
-module.exports = {
+const config = {
   quoteProps: 'as-needed',
   singleQuote: true,
   tabWidth: 2,
   trailingComma: 'all',
+  plugins: ['prettier-plugin-packagejson'],
 };
+
+export default config;

.prettierrc.js .prettierrc.mjs.prettierrc.js renamed to .prettierrc.mjs

@@ -14,4 +14,4 @@ nodeLinker: node-modules
 
 plugins:
   - path: .yarn/plugins/@yarnpkg/plugin-allow-scripts.cjs
-    spec: 'https://raw.githubusercontent.com/LavaMoat/LavaMoat/main/packages/yarn-plugin-allow-scripts/bundles/@yarnpkg/plugin-allow-scripts.js'
+    spec: "https://raw.githubusercontent.com/LavaMoat/LavaMoat/main/packages/yarn-plugin-allow-scripts/bundles/@yarnpkg/plugin-allow-scripts.js"

.yarnrc.yml

@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+
+- **BREAKING:** Distribute separate CommonJS and ESM files ([#351](https://github.com/MetaMask/eth-block-tracker/pull/351))
+  - Use the `exports` field of `package.json`, breaking some previously valid imports.
+
 ## [12.2.1]
 
 ### Fixed

CHANGELOG.md

@@ -106,35 +106,28 @@ Run `yarn lint` to run the linter, or run `yarn lint:fix` to run the linter and
 The project follows the same release process as the other libraries in the MetaMask organization. The GitHub Actions [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) and [`action-publish-release`](https://github.com/MetaMask/action-publish-release) are used to automate the release process; see those repositories for more information about how they work.
 
 1. Choose a release version.
-
    - The release version should be chosen according to SemVer. Analyze the changes to see whether they include any breaking changes, new features, or deprecations, then choose the appropriate SemVer version. See [the SemVer specification](https://semver.org/) for more information.
 
 2. If this release is backporting changes onto a previous release, then ensure there is a major version branch for that version (e.g. `1.x` for a `v1` backport release).
-
    - The major version branch should be set to the most recent release with that major version. For example, when backporting a `v1.0.2` release, you'd want to ensure there was a `1.x` branch that was set to the `v1.0.1` tag.
 
 3. Trigger the [`workflow_dispatch`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch) event [manually](https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow) for the `Create Release Pull Request` action to create the release PR.
-
    - For a backport release, the base branch should be the major version branch that you ensured existed in step 2. For a normal release, the base branch should be the main branch for that repository (which should be the default value).
    - This should trigger the [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) workflow to create the release PR.
 
 4. Update the changelog to move each change entry into the appropriate change category ([See here](https://keepachangelog.com/en/1.0.0/#types) for the full list of change categories, and the correct ordering), and edit them to be more easily understood by users of the package.
-
    - Generally any changes that don't affect consumers of the package (e.g. lockfile changes or development environment changes) are omitted. Exceptions may be made for changes that might be of interest despite not having an effect upon the published package (e.g. major test improvements, security improvements, improved documentation, etc.).
    - Try to explain each change in terms that users of the package would understand (e.g. avoid referencing internal variables/concepts).
    - Consolidate related changes into one change entry if it makes it easier to explain.
    - Run `yarn auto-changelog validate --rc --prettier` to check that the changelog is correctly formatted.
 
 5. Review and QA the release.
-
    - If changes are made to the base branch, the release branch will need to be updated with these changes and review/QA will need to restart again. As such, it's probably best to avoid merging other PRs into the base branch while review is underway.
 
 6. Squash & Merge the release.
-
    - This should trigger the [`action-publish-release`](https://github.com/MetaMask/action-publish-release) workflow to tag the final release commit and publish the release on GitHub.
 
 7. Publish the release on npm.
-
    - Be very careful to use a clean local environment to publish the release, and follow exactly the same steps used during CI.
    - Use `npm publish --dry-run` to examine the release contents to ensure the correct files are included. Compare to previous releases if necessary (e.g. using `https://unpkg.com/browse/[package name]@[package version]/`).
    - Once you are confident the release contents are correct, publish the release using `npm publish`.

README.md

@@ -0,0 +1,60 @@
+import base, { createConfig } from '@metamask/eslint-config';
+import jest from '@metamask/eslint-config-jest';
+import nodejs from '@metamask/eslint-config-nodejs';
+import typescript from '@metamask/eslint-config-typescript';
+
+const config = createConfig([
+  {
+    ignores: ['dist/', 'docs/', '.yarn/'],
+  },
+
+  {
+    extends: base,
+
+    languageOptions: {
+      sourceType: 'module',
+      parserOptions: {
+        tsconfigRootDir: import.meta.dirname,
+        project: ['./tsconfig.json'],
+      },
+    },
+
+    settings: {
+      'import-x/extensions': ['.js', '.mjs'],
+    },
+  },
+
+  {
+    files: ['**/*.ts'],
+    extends: typescript,
+    rules: {
+      // TODO: These should perhaps be enabled
+      '@typescript-eslint/prefer-nullish-coalescing': 'off',
+      'no-restricted-syntax': 'off',
+      // TODO: Thise should definitely be enabled
+      '@typescript-eslint/naming-convention': 'warn',
+      '@typescript-eslint/unbound-method': 'warn',
+      '@typescript-eslint/consistent-type-definitions': 'warn',
+      '@typescript-eslint/explicit-function-return-type': 'warn',
+    },
+  },
+
+  {
+    files: ['**/*.js', '**/*.cjs'],
+    extends: nodejs,
+
+    languageOptions: {
+      sourceType: 'script',
+    },
+  },
+
+  {
+    files: ['./test/**/*', '**/*.test.ts', '**/*.test.js'],
+    extends: [jest, nodejs],
+    rules: {
+      'import-x/no-nodejs-modules': 'off',
+    },
+  },
+]);
+
+export default config;