Importing zx library in RSC causes bundler error
#76637
Comments
|
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully. Why was this issue closed?To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need 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. The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
What should I do?Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue. My repository is private and cannot make it publicIn most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
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 by opening a new issue. I think my reproduction is good enough, why aren't you looking into it quickly?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 |
|
It's cuz that package does this:
export const VERSION: string = fs.readJsonSync(
new URL('../package.json', import.meta.url)
).versionBecause the page file is compiled, and run from within the There's a solution though!/** @type {import('next').NextConfig} */
const nextConfig = {
serverExternalPackages: ['zx'],
};Relevant docs: https://nextjs.org/docs/app/api-reference/config/next-config-js/serverExternalPackages |
|
Copying my reply from #76639 (reply in thread): Interesting! And unfortunate. I can appreciate the optimization aspect, but it seems like Next.js (or webpack?) is making unsafe assumptions about the code it's touching. I was lucky to run into this particular error during dev, but there could be similar errors that go undiscovered until they are hit in production.
I think unsafe behavior should be opt-in instead of opt-out. At the very least, Next.js / webpack should use more heuristics, such as checking for usage of |
Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/priceless-forest-xjdq86
To Reproduce
Run
pnpm install zx.Reference any
zxfunction in a server component (or in library code called by a server component). It is only necessary to reference the function, not call it. For example:Visit the page, and observe the "ENOENT: no such file or directory, open '/project/workspace/.next/server/package.json'" error.
Full stack trace
Current vs. Expected behavior
I expect to be able to use
zxin server-side code.The current behavior causes an
ENOENTerror when anyzxexport is referenced.Provide environment information
Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023 Available memory (MB): 4242 Available CPU cores: 2 Binaries: Node: 20.9.0 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.10.2 Relevant Packages: next: 15.2.1-canary.1 // Latest available version is detected (15.2.1-canary.1). eslint-config-next: N/A react: 19.0.0 react-dom: 19.0.0 typescript: 5.3.3 Next.js Config: output: N/AWhich area(s) are affected? (Select all that apply)
Turbopack, Webpack
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local)
Additional context
(This is a retry of #76636, which the bot erroneously closed.)
zxis a library by Google that provides various utility functions for interacting with the file system and OS. For example, aglobfunction and functions for colorizing log messages.The text was updated successfully, but these errors were encountered: