search

vercel / next.js

The React Framework
https://nextjs.org
MIT License
127.07k stars 27.01k forks source link

TypeError: Cannot read properties of undefined (reading 'length') #50388

Closed michael-land closed 1 year ago

michael-land commented 1 year ago

Verify canary release

/** @type {import('next').NextConfig} */
export default {
  experimental: {
    appDir: true,
    serverActions: true,
  },
};
- error uncaughtException: TypeError: Cannot read properties of undefined (reading 'length')
    at WasmHash._updateWithBuffer (/Users/./hubspot-kit/monorepo3/node_modules/.pnpm/next@13.4.5-canary.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:28:1352524)
    at WasmHash.update (/Users/./hubspot-kit/monorepo3/node_modules/.pnpm/next@13.4.5-canary.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:28:1351859)
    at BatchedHash.update (/Users/./hubspot-kit/monorepo3/node_modules/.pnpm/next@13.4.5-canary.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:28:1348216)
    at /Users/./hubspot-kit/monorepo3/node_modules/.pnpm/next@13.4.5-canary.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:28:292480
    at processQueue (/Users/./hubspot-kit/monorepo3/node_modules/.pnpm/next@13.4.5-canary.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/webpack/bundle5.js:28:1365665)
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

After updating to version 13.4.4, the "next dev" no longer functions. Has anyone else experienced this issue, or is it just me?

marozzocom commented 1 year ago

I can confirm having same issue on 13.4.4 and 13.4.5-canary.0. Reverting to 13.4.3 removed the error.

github-actions[bot] commented 1 year ago

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 pages, template for App Router), but you can also use these templates: CodeSandbox: pages or CodeSandbox: App 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.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

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 :+1: 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

balazsorban44 commented 1 year ago

Closing this issue. Please open a new one with the reproduction steps and don't ignore the issue template. 🙏 this will let us investigate the issue much faster and will result in a faster resolution for you too. Thanks!

Torsten85 commented 1 year ago

I had the same error.. as it turns out I had a misconfiguration in my tailwind.config.cjs!

I'm also working in a pnpm monorepo and I need tailwind to include a specific dependency as content, so I added ./node_modules/my-other-package/**/*.{ts,tsx} to the configuration. But that also included every dependency of my-other-package (./node_modules/my-package/node_modules/**). And those dependency are links to the pnpm store... I guess at some point, the bundle simply gave up 😉

Long story short, changing the content in my tailwindconfig to ./node_modules/my-other-package/src/**/*{.ts,tsx} did the trick for me.

stevejcox commented 1 year ago

We're seeing the WasmHash error back in 13.4.4

awilderink commented 1 year ago

I had the same error.. as it turns out I had a misconfiguration in my tailwind.config.cjs!

I'm also working in a pnpm monorepo and I need tailwind to include a specific dependency as content, so I added ./node_modules/my-other-package/**/*.{ts,tsx} to the configuration. But that also included every dependency of my-other-package (./node_modules/my-package/node_modules/**). And those dependency are links to the pnpm store... I guess at some point, the bundle simply gave up 😉

Long story short, changing the content in my tailwindconfig to ./node_modules/my-other-package/src/**/*{.ts,tsx} did the trick for me.

Life saver, exactly the same setup for me and this fixed it. Weird it didn't occur before updating to 13.4.4

github-actions[bot] commented 1 year ago

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.