Comments (6)
We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.
Why was this issue marked with the please add a complete reproduction
label?
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.
To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.
Please test your reproduction against the latest version of Next.js (next@canary
) to make sure your issue has not already been fixed.
If you cannot create a clean reproduction, another way you can help the maintainers' job is to pinpoint the canary
version of next
that introduced the issue. Check out our releases, and try to find the first canary
release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next
by running npm install next@<version>
.
I added a link, why was it still marked?
Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.
What happens if I don't provide a sufficient minimal reproduction?
Issues with the please add a complete reproduction
label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.
If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.
I did not open this issue, but it is relevant to me, what can I do to help?
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.
I think my reproduction is good enough, why aren't you looking into it quicker?
We look into every Next.js issue and constantly monitor open issues for new comments.
However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.
Useful Resources
- How to Contribute to Open Source (Next.js)
- How to create a Minimal, Complete, and Verifiable example
- Reporting a Next.js bug
- Next.js Triaging issues
from next.js.
Seems you've copy-pasted the sandbox and didn't add any code into it, in the future please double check that the provided reproduction actually reproduces the issue.
from next.js.
Here's a sandbox of the reproduction steps working fine on next@latest
: https://codesandbox.io/p/devbox/sleepy-bassi-stw4yq?file=%2Fapp%2Fpage.tsx%3A7%2C1&workspaceId=062b139a-c054-40fe-bbf5-0210d48b9dd0. Also verified next@canary
.
from next.js.
Sorry for the wrong code sandbox link.
Here is the updated one: https://codesandbox.io/p/devbox/old-resonance-lv6j3x
The reproduction steps only working fine if highlight.js
is specified as dependencies in package.json
.
Without adding highlight.js
in package.json. highlight.js
is still installed in node_module and resolved in lockfile. next dev --turbo
will fail to compile, but next dev
can.
from next.js.
Thank for the reproduction! Was able to figure out what the problem is based on that.
So the problem is that webpack resolving in this particular case is incorrect, it allows you to import modules from a place that your application code shouldn't have access to, namely the node_modules of a nested dependency. Turbopack has a more correct resolving that matches closer to what Node.js does. If you try running the Node.js repl you'll notice that import('highlight.js/lib/languages/typescript')
Looking at the docs for the package you'll want to do something like this instead as lowlight includes the highlight.js data:
import { createLowlight, common } from "lowlight";
const lowlight = createLowlight();
lowlight.register({ typescript: common.typescript });
Lowlight also exports all
for all of the languages, keep in mind those are all bundled, best to keep them in a server component.
from next.js.
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
from next.js.
Related Issues (20)
- Dev server stuck on state - "Cannot read properties of null (reading 'useContext')" HOT 1
- Next [14.2.3] Custom headers not working when using redirect in middleware HOT 5
- Next >14.0.1 cannot use @ant-design/icons (unexpected token 'export')
- API Route Inside Dockerized App Repeating Results HOT 1
- Docs: inconsistency for config matcher docs
- App router routing to dynamic route instead of predefined route in Next.js HOT 3
- Can not deploy Next.js app HOT 1
- Docs: Add explanation why CacheHandler.revalidateTag never gets called using Pages Router
- `<Link` breaking when there is padding or margin attached HOT 3
- Page props not passed for Index page when Middleware and basePath in use
- [Middleware] Locale in NextResponse.rewrite(...) path ignored for dynamic routes when basepath is set and skipMiddlewareUrlNormalize is true
- Not working with Yarn pnpm strategy
- server action compiler error is thrown when `graphql` relay tags are used HOT 6
- Double redirect in RSC page when using a loading boundary HOT 6
- Edge Runtime and AWS SDK credentials
- Application error: a client-side exception has occurred HOT 1
- Canonical link doesn't accept search params on root path
- next build throws `Error: <Html> should not be imported outside of _document` after 1 month, and no changes made to the code or build environment HOT 1
- Rsc header and query params always null on middleware
- NODE_OPTIONS='--inspect=0.0.0.0:9229' next dev no work HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from next.js.