15.4.1 turbopack panic AliasMap::lookup must not be called on alternatives, received Alternatives
Unanswered
Pacific anchoveta posted this in #help-forum
Pacific anchovetaOP
Anyone experience this issue after upgrading to 15.4.1 (from 15.3.5) on compiling app route in dev --turbo?
thread 'tokio-runtime-worker' panicked at turbopack/crates/turbopack-core/src/resolve/alias_map.rs:206:13:
AliasMap::lookup must not be called on alternatives, received Alternatives([Dynamic, Constant("null")])
stack backtrace:
0: 0x1658d992c - _napi_register_module_v1
1: 0x1658fd968 - _napi_register_module_v1
2: 0x1658d48c8 - _napi_register_module_v1
3: 0x1658d97e0 - _napi_register_module_v1
4: 0x1658dbe38 - _napi_register_module_v1
5: 0x1658dbc88 - _napi_register_module_v1
6: 0x1658dc938 - _napi_register_module_v1
7: 0x1658dc528 - _napi_register_module_v1
8: 0x1658d9df0 - _napi_register_module_v1
9: 0x1658dc1d0 - _napi_register_module_v1
10: 0x165a4e8ac - _napi_register_module_v1
11: 0x163f5af9c - _BrotliDecoderVersion
12: 0x164076f7c - _BrotliDecoderVersion
13: 0x16407c68c - _BrotliDecoderVersion
14: 0x164025750 - _BrotliDecoderVersion
15: 0x163fdaf4c - _BrotliDecoderVersion
16: 0x163fb91d8 - _BrotliDecoderVersion
17: 0x160a13aac - <unknown>
18: 0x160a6f35c - <unknown>
19: 0x160a3b730 - <unknown>
20: 0x160a3a680 - <unknown>
21: 0x160a6eea0 - <unknown>
22: 0x1608092c8 - <unknown>
23: 0x160713d2c - <unknown>
24: 0x160720db0 - <unknown>
25: 0x160721164 - <unknown>
26: 0x1658992ac - _napi_register_module_v1
27: 0x1658987f8 - _napi_register_module_v1
28: 0x165880400 - _napi_register_module_v1
29: 0x16587ff00 - _napi_register_module_v1
30: 0x165898028 - _napi_register_module_v1
31: 0x165887d68 - _napi_register_module_v1
32: 0x165892d90 - _napi_register_module_v1
33: 0x1658690ac - _napi_register_module_v1
34: 0x165863168 - _napi_register_module_v1
35: 0x1658869a0 - _napi_register_module_v1
36: 0x1658734e0 - _napi_register_module_v1
37: 0x16586bec4 - _napi_register_module_v1
38: 0x16586c278 - _napi_register_module_v1
39: 0x1658ded50 - _napi_register_module_v1
40: 0x19ef96c0c - __pthread_cond_wait
thread 'tokio-runtime-worker' panicked at turbopack/crates/turbopack-core/src/resolve/alias_map.rs:206:13:
AliasMap::lookup must not be called on alternatives, received Alternatives([Dynamic, Constant("null")])
stack backtrace:
0: 0x1658d992c - _napi_register_module_v1
1: 0x1658fd968 - _napi_register_module_v1
2: 0x1658d48c8 - _napi_register_module_v1
3: 0x1658d97e0 - _napi_register_module_v1
4: 0x1658dbe38 - _napi_register_module_v1
5: 0x1658dbc88 - _napi_register_module_v1
6: 0x1658dc938 - _napi_register_module_v1
7: 0x1658dc528 - _napi_register_module_v1
8: 0x1658d9df0 - _napi_register_module_v1
9: 0x1658dc1d0 - _napi_register_module_v1
10: 0x165a4e8ac - _napi_register_module_v1
11: 0x163f5af9c - _BrotliDecoderVersion
12: 0x164076f7c - _BrotliDecoderVersion
13: 0x16407c68c - _BrotliDecoderVersion
14: 0x164025750 - _BrotliDecoderVersion
15: 0x163fdaf4c - _BrotliDecoderVersion
16: 0x163fb91d8 - _BrotliDecoderVersion
17: 0x160a13aac - <unknown>
18: 0x160a6f35c - <unknown>
19: 0x160a3b730 - <unknown>
20: 0x160a3a680 - <unknown>
21: 0x160a6eea0 - <unknown>
22: 0x1608092c8 - <unknown>
23: 0x160713d2c - <unknown>
24: 0x160720db0 - <unknown>
25: 0x160721164 - <unknown>
26: 0x1658992ac - _napi_register_module_v1
27: 0x1658987f8 - _napi_register_module_v1
28: 0x165880400 - _napi_register_module_v1
29: 0x16587ff00 - _napi_register_module_v1
30: 0x165898028 - _napi_register_module_v1
31: 0x165887d68 - _napi_register_module_v1
32: 0x165892d90 - _napi_register_module_v1
33: 0x1658690ac - _napi_register_module_v1
34: 0x165863168 - _napi_register_module_v1
35: 0x1658869a0 - _napi_register_module_v1
36: 0x1658734e0 - _napi_register_module_v1
37: 0x16586bec4 - _napi_register_module_v1
38: 0x16586c278 - _napi_register_module_v1
39: 0x1658ded50 - _napi_register_module_v1
40: 0x19ef96c0c - __pthread_cond_wait
7 Replies
Giant panda
getting the same issues
i had to downgrade to 15.3.5
Eulophid wasp
Known issue, it's being fixed: https://github.com/vercel/next.js/issues/81628#issuecomment-3073199222
Just stick to 15.3.5 for now, I haven't been able to find a workaround
@Eulophid wasp Known issue, it's being fixed: https://github.com/vercel/next.js/issues/81628#issuecomment-3073199222
Pacific anchovetaOP
Hmm this issue seems unrelated or am i not seeing where the issue can be shown to be the same issue?
@Pacific anchoveta Hmm this issue seems unrelated or am i not seeing where the issue can be shown to be the same issue?
Eulophid wasp
Sorry, I was seeing the same kind of output in 15.4. If you're not in a monorepo then it's likely another issue
Pacific anchovetaOP
At least error messages and symptoms look very different in that issye, but im sure there is a fix on the way in any case in the next few minor releases