tailwindcss-animate should be a dev dependency
#703
Conversation
Updated client dependencies to ensure compatibility with latest versions. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
phuctm97
changed the title
tailwindcss-animate should be a dev dependency
| @@ -72,6 +71,7 @@ | |||
| "jest-environment-jsdom": "^29.7.0", | |||
| "postcss": "^8.5.6", | |||
| "tailwindcss": "^3.4.13", | |||
| "tailwindcss-animate": "^1.0.7", | |||
There was a problem hiding this comment.
Hi, looking at the build, it looks like this might be used in the build process - how did you determine that it only needs to be in devDependencies? This branch seems to build locally for me, but haven't checked yet to see if it might be needed for CICD.
There was a problem hiding this comment.
Putting tailwindcss-animate in dependencies means that any package that uses the published @modelcontextprotocol/inspector npm package must also install tailwindcss-animate and all of its dependencies.
The published @modelcontextprotocol/inspector npm package contains only already-built code. All dependencies that are used to build/produce the final @modelcontextprotocol/inspector package content doesn't need to be installed in downstream projects to be able to use @modelcontextprotocol/inspector package.
Put simply, any packages that are only used to build a package should be a devDependency and not a dependency.
tailwindcss-animatetodevDependenciesin client package.json