search

vercel / next.js

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

Turbo pack not working ion next 15 #71707

Closed TudorEsan closed 3 hours ago

TudorEsan commented 3 hours ago

Link to the code that reproduces this issue

can't because its production code

To Reproduce

ran next dev --turbo

Current vs. Expected behavior

ran next dev --turbo should not result in a fatal error

Provide environment information

FATAL: An unexpected Turbopack error occurred. Please report the content of /var/folders/_y/p5f3w4394pq2z9j58m35rlfh0000gn/T/next-panic-55221bbfd547e100a4fc8a0160c7634.log to https://github.com/vercel/next.js/issues/new
[Error: A task panicked: range end index 6 out of range for slice of length 5

Debug info:
- Execution of get_entrypoints_with_issues failed
- Execution of Project::entrypoints failed
- Execution of AppProject::routes failed
- Execution of directory_tree_to_entrypoints_internal failed
- Execution of directory_tree_to_entrypoints_internal failed
- Execution of directory_tree_to_entrypoints_internal failed
- A task panicked: range end index 6 out of range for slice of length 5] {
  name: 'TurbopackInternalError'
}
-------------------- logs

---------------------------
Panic: panicked at crates/next-core/src/next_app/metadata/mod.rs:277:11:
range end index 6 out of range for slice of length 5
Backtrace:    0: _napi_register_module_v1
   1: <unknown>
   2: _napi_register_module_v1
   3: _napi_register_module_v1
   4: _napi_register_module_v1
   5: _napi_register_module_v1
   6: _napi_register_module_v1
   7: _napi_register_module_v1
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: _napi_register_module_v1
  23: _napi_register_module_v1
  24: _napi_register_module_v1
  25: _napi_register_module_v1
  26: _napi_register_module_v1
  27: _napi_register_module_v1
  28: _napi_register_module_v1
  29: _napi_register_module_v1
  30: _napi_register_module_v1
  31: _napi_register_module_v1
  32: _napi_register_module_v1
  33: _napi_register_module_v1
  34: _napi_register_module_v1
  35: __pthread_deallocate

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

i can't run next with turbopack, it always breaks with this error:

FATAL: An unexpected Turbopack error occurred. Please report the content of /var/folders/_y/p5f3w4394pq2z9j58m35rlfh0000gn/T/next-panic-55221bbfd547e100a4fc8a0160c7634.log to https://github.com/vercel/next.js/issues/new
[Error: A task panicked: range end index 6 out of range for slice of length 5

Debug info:
- Execution of get_entrypoints_with_issues failed
- Execution of Project::entrypoints failed
- Execution of AppProject::routes failed
- Execution of directory_tree_to_entrypoints_internal failed
- Execution of directory_tree_to_entrypoints_internal failed
- Execution of directory_tree_to_entrypoints_internal failed
- A task panicked: range end index 6 out of range for slice of length 5] {
  name: 'TurbopackInternalError'
}

next.config.js

const { withSentryConfig } = require('@sentry/nextjs');

const withBundleAnalyzer = require('@next/bundle-analyzer')({
  enabled: process.env.ANALYZE === 'true',
});

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: config => {
    config.externals.push('pino-pretty', 'lokijs', 'encoding');
    return config;
  },
  images: {
    remotePatterns: [
      {
        protocol: 'https',
        hostname: '**',
      },
    ],
    unoptimized: true,
  },
};

let config = withBundleAnalyzer(nextConfig);

// Injected content via Sentry wizard below

config = withSentryConfig(
  config,
  {
    silent: true,
    org: 'pulsar-money',
    project: 'evm-client',
  },
  {
    widenClientFileUpload: true,
    transpileClientSDK: true,
    tunnelRoute: '/monitoring',
    hideSourceMaps: true,
    disableLogger: true,
    automaticVercelMonitors: true,
    // Additional options...
  }
);

module.exports = config;
github-actions[bot] commented 3 hours ago

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 public

In 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