Clean up Install Warnings

[bh2smith]

PR Type

enhancement, configuration changes

---

Description

• Added resolutions field in package.json to specify versions for glob and base-x packages, addressing potential installation warnings.
• Reformatted tsconfig.json for improved readability without altering configuration values.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	package.json Add resolutions for specific package versions                        package.json Added resolutions field to specify versions for glob and base-x packages. +4/-0
Enhancement	tsconfig.json Reformat tsconfig.json for better readability                        tsconfig.json Reformatted the JSON structure for better readability. No changes to the actual configuration values. +24/-17

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[mintbase-codium-pr-agent]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[mintbase-codium-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Enable library check to ensure type safety It is recommended to remove the skipLibCheck option or set it to false to ensure type safety. This option skips type checking of all declaration files (*.d.ts), which can potentially hide useful error messages and lead to runtime errors that are difficult to debug. tsconfig.json [25] -"skipLibCheck": true +"skipLibCheck": false Suggestion importance[1-10]: 9 Why: Enabling library checks can catch type errors in declaration files, which improves overall type safety and helps prevent runtime errors. This is a significant improvement for maintaining code quality.	9
	Use exact versions for dependencies to avoid potential inconsistencies Consider specifying exact versions for the resolutions of glob and base-x to avoid potential inconsistencies caused by unexpected updates. Using exact versions can help ensure that everyone working on the project has the same dependencies, which can lead to fewer "works on my machine" bugs. package.json [68-69] -"glob": "^9.0.0", -"base-x": "^3.0.0" +"glob": "9.0.0", +"base-x": "3.0.0" Suggestion importance[1-10]: 8 Why: Using exact versions for dependencies can help ensure consistency across different environments, reducing the likelihood of "works on my machine" bugs. This is a best practice for maintaining stable builds.	8
Enhancement	Re-enable rigorous type checking for indexed access Consider re-enabling the noUncheckedIndexedAccess option to provide more rigorous type checking. This option adds undefined to the type of every index signature result, which can help catch null reference errors during development. tsconfig.json [23] -// TODO: Add this back! -// "noUncheckedIndexedAccess": true, +"noUncheckedIndexedAccess": true, Suggestion importance[1-10]: 7 Why: Re-enabling noUncheckedIndexedAccess enhances type safety by catching potential null reference errors. This suggestion improves code robustness but is less critical than enabling library checks.	7
Maintainability	Optimize the exclude patterns in tsconfig to simplify the configuration The include and exclude patterns can be optimized by removing redundant entries. For instance, specifying node_modules and dist in exclude is usually enough, as other directories like examples, tests, and eslint.config.cjs might not contain TypeScript files or can be covered by other rules in your build configuration. tsconfig.json [31-36] "exclude": [ "node_modules", - "dist", - "examples", - "tests", - "eslint.config.cjs" + "dist" ] Suggestion importance[1-10]: 6 Why: Simplifying the exclude patterns can make the configuration cleaner and easier to maintain. However, this is a minor improvement compared to the other suggestions.	6