Skip to content

chore: remove unused next-logger and server-only deps - #1417

Open
digitalbase wants to merge 2 commits into
mainfrom
remove-unused-deps-next-logger-server-only
Open

chore: remove unused next-logger and server-only deps#1417
digitalbase wants to merge 2 commits into
mainfrom
remove-unused-deps-next-logger-server-only

Conversation

@digitalbase

Copy link
Copy Markdown
Contributor

Summary

  • Remove server-only from runtime dependencies and lockfile because it has no imports.
  • Remove next-logger from dev dependencies and lockfile because it has no code/config usage.
  • Keep dependency manifest aligned with actual usage to reduce maintenance overhead.

Testing

  • Not run (dependency manifest + lockfile cleanup only).

@marie-hermes-agent marie-hermes-agent Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean dependency removal. Verify no imports remain in the codebase.

Comment thread package.json
"react-dom": "19.2.4",
"react-instantsearch-dom": "6.40.4",
"server-only": "0.0.1",
"social-links": "1.15.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good removal of server-only. This package is typically used to mark modules as server-only in Next.js App Router. Ensure no files in the codebase still have import 'server-only' statements, as this would cause runtime errors.

Comment thread package.json
"autoprefixer": "10.4.21",
"dotenv": "^16.4.7",
"next-logger": "5.0.1",
"np": "10.2.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing next-logger from devDependencies. This was likely used for structured logging in Next.js. Verify that:

  1. No import statements for next-logger remain in the codebase
  2. Any logging configuration files (like next-logger.config.js) are also removed
  3. The application still has adequate logging in place

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant