Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: Cleaner support for NextJS

Open
  • Is something wrong?
#159 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
nextjs, typescript
Domain
build-system, tooling

Research direction

Start by reading the package that provides the current Next.js support and the discussion in pull request #157. Compare the desired default wrapper API with @next/bundle-analyzer, then check how it interacts with next-compose-plugins. Done means the wrapper API is exposed and compatibility is verified.

Written by the indexing model from the issue text.

Description

          Given we have a specific package now, we can also expose a wrapper API like `@next/bundle-analyzer` does: https://www.npmjs.com/package/@next/bundle-analyzer

So the API would be export default withCodecov(...)

We should just make sure it's compatible with https://github.com/cyrilwanner/next-compose-plugins.

Originally posted by @AbhiPrasad in https://github.com/codecov/codecov-javascript-bundler-plugins/pull/157#discussion_r1731392275

Dominant language
TypeScript
Stars
9
Forks
10
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codecov/codecov-javascript-bundler-plugins

All issues in codecov/codecov-javascript-bundler-plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.