changeset-bot[bot]
commented
7 months ago ⚠️ No Changeset found
Latest commit: 28b067ff115e4ef9dae6bdc5041d08efb9272803
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver typesClick here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
This pull request includes updates to the tsconfig.json file, aligning it with modern development practices. The changes introduced are as follows:
Changes
"moduleResolution": "Bundler": This option is configured for use with bundlers. Unlike the Node.js resolution modes, this setting supports package.json "imports" and "exports" without requiring file extensions on relative paths in imports."moduleDetection": "force": Enabling this option ensures that every non-declaration file is treated as a module, providing a more consistent and predictable module handling approach."isolatedModules": true: TypeScript will now issue warnings for code that might not be correctly interpreted by a single-file transpilation process, helping catch potential issues early in the development process."verbatimModuleSyntax": true: Forces type imports to be flagged with atypemodifier. This is particularly useful for bundlers, as it signals upfront that the code won't be used as a value, allowing the bundler to exclude it from the generated JavaScript code."lib": ["ES2022"]: Updated to include only APIs from ES2022, explicitly excluding DOM APIs.