Check a codebase for redundant packages and polyfills

An agent can scan code and install commands to find dependencies that can be replaced with built-ins or better options.

Done with Custom agent· Intermediate

What they did
A developer connected the e18e MCP server to their agent, either through a remote HTTP setup or by using the local @e18e/mcp package. After that, the agent could review install commands, inspect source files for import substitutions, search by package name or topic, and open migration guides.
How it went
The setup description does not show a real audit result, so there is no evidence of how many packages were flagged or removed. It also notes that the checker handles one source file at a time, which means a full repository needs file-by-file review.
Tips
Use it as a review tool, not an auto-fixer. Ask the agent to pause before any changes to package files or installs, and have it work through the repo one file at a time.

Try it yourself with Claude Code

Review the code at [repo path] for dependencies and polyfills that look unnecessary in [runtime/version]. Check install commands, source imports, and any obvious built-in replacements. List each item with the current package, why it seems redundant, and a safer replacement; then stop and ask me to approve before you change any package files, delete anything, or run installs.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.