The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Co-authored-by: sirreal <jonsurrell@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

I read about jsconfig here and I think it should probably be removed. My concern is that there are a number of packages that do not have tsconfig.json and would not be covered.

find packages -mindepth 1 -maxdepth 1 -type d '!' -exec sh -c 'ls -1 "{}"|grep -E -i -q "^tsconfig.json$"' ';' -print

packages/readable-js-assets-webpack-plugin
packages/format-library
packages/blocks
packages/preferences-persistence
packages/jest-puppeteer-axe
packages/interface
packages/preferences
packages/viewport
packages/server-side-render
packages/react-native-aztec
packages/patterns
packages/babel-plugin-makepot
packages/react-native-bridge
packages/browserslist-config
packages/postcss-plugins-preset
packages/dependency-extraction-webpack-plugin
packages/babel-plugin-import-jsx-pragma
packages/e2e-test-utils
packages/edit-widgets
packages/edit-site
packages/create-block
packages/nux
packages/npm-package-json-lint-config
packages/block-directory
packages/create-block-interactive-template
packages/env
packages/e2e-tests
packages/stylelint-config
packages/annotations
packages/react-native-editor
packages/base-styles
packages/list-reusable-blocks
packages/postcss-themes
packages/jest-console
packages/scripts
packages/core-commands
packages/block-serialization-spec-parser
packages/customize-widgets
packages/commands
packages/edit-post
packages/jest-preset-default
packages/babel-preset-default
packages/create-block-tutorial-template
packages/reusable-blocks
packages/widgets
packages/keyboard-shortcuts

Should these packages first get a basic tsconfig.json file and be added to the main tsconfig?

Flaky tests detected in eb4da08.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12515496285
📝 Reported issues:

• [Flaky Test] Navigates the items list via UP/DOWN arrow keys #64334 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js
• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

My concern is that there are a number of packages that do not have tsconfig.json and would not be covered.

It was added in #8043 to have IntelliSense, which should still work because we declare the dependencies in package.json for each package and we now use npm workspaces, which inegrates even better.

Here is an example in server-side-render package which doesn't have a tsconfig.json file