Highlight files in package file browser that may be included accidentally/unnecessarily

[connorshea]

Describe the feature

In the package code browser, highlight files which may be accidental/unnecessary inclusions in the released package. This would help prevent package bloat / make it easier to identify.

For example, generally you wouldn't want to ship a .claude/settings.json or .claude/settings.local.json file in your package. You probably also don't want to ship a .vscode/launch.json file, or .vscode/settings.json. These files are generally meant for local development.

Maybe also surface this information elsewhere, to show optimization opportunities in the package, but I'm not sure how/where that should be put. It's not necessarily a huge problem to include these files (usually they are small / don't have anything sensitive). And I don't want to end up with people making tons of issues for maintainers like "why do you include this file that's 100 bytes?", but it'd be nice to surface somehow.

Directories like test/ or tests/ are generally not meant to be included in the published package, and could be highlighted as well.

For example, the resolve package has a claude directory, tests, and .editorconfig: https://npmx.dev/package-code/resolve/v/1.22.12

and ts-log v2.x had .vscode/settings.json (which actually caused me weird problems with Claude Code's sandbox being unwilling to even pnpm install due to files named settings.json not being allowed to be created/edited by the sandbox process): https://npmx.dev/package-code/ts-log/v/2.2.7/.vscode

---

List of possible inclusions for the files/directories to check and warn on:

• .editorconfig
• .github/ (except maybe FUNDING.yml? idk if that's something that is used by package managers)
• .vscode/
• .prettierignore
• .eslintignore
• .gitignore
• .gitattributes
• test/, tests/, etc.
• .claude/
• tsconfig.json
• .eslintrc / eslint.config.js / eslint.config.mjs / etc
• oxlint.config.ts / .oxlintrc.json / oxfmt.config.ts / .oxfmtrc.json
• prettierrc.yml / .prettierrc / prettierrc.json / etc
• .node-version
• mise.toml
• .env
• .env.local
• .nycrc / nyc.json, etc

Additional information

• Would you be willing to help implement this feature?

Final checks

• Read the contribution guide.
• Check existing issues.

[snakefood3232]

You mentioned highlighting files like .claude/settings.json and test/ in the package browser to prevent accidental inclusions. I'd handle this by adding a visual indicator and a filter for development/config files, referencing common .npmignore patterns. Can have a PR ready for review within a day—I've implemented similar file classification systems in other code browsers.