Link failed due to the unknown "default"

[YellowRiver6]

What happened

compile my repo "Funkin-Online-Server-Perry" using perry but link failed

What you expected

I want to know what these "default" are.

Minimal reproduction

In my repo

Command you ran:

perry compile src/index.ts -o main

Environment

• Perry version: 0.5.585
• Host OS: Ubuntu 26.04
• Target: native
• Rust toolchain (if building from source): stable 1.95.0
• Installed via: from source

Diagnostic output

Using V8 JavaScript runtime for JS module support
/usr/bin/x86_64-linux-gnu-ld.bfd: network_database_ts.o: in function `perry_closure_network_database_ts__342':
perry_llvm_20081_1778514024088078839.ll:(.text+0x3af81): undefined reference to `default'
/usr/bin/x86_64-linux-gnu-ld.bfd: network_database_ts.o: in function `perry_closure_network_database_ts__480':
perry_llvm_20081_1778514024088078839.ll:(.text+0x5367c): undefined reference to `default'
collect2: error: ld returned 1 exit status
Error: Linking failed

Anything else

[proggeramlug]

Thanks for the report! You're on 0.5.585, but we've shipped 256 versions since — including several fixes around default-import handling and cjs-wrap closure capture (most recently v0.5.839 for default-key tracking through import X from '...'). The undefined reference to 'default' pattern strongly suggests one of those code paths.

Could you:

1. Update to latest (0.5.841) and re-run, and
2. If it still fails, share a minimal repro — even one of the failing .ts files plus its imports trimmed to just the closure that fails. The closures by index are network_database_ts__342 and __480; if you can --print-hir or share which function bodies those map to, that pins it down fast.

[YellowRiver6]

I update to perry 0.5.853 and re-run. but the "default"s still exist.
And there is a new compile error with 0.5.853 "Error: axios.NotFound is not implemented in Perry — see perry --print-api-manifest for the supported surface, or set PERRY_ALLOW_UNIMPLEMENTED=1 to ignore. (#463)"

run the command

PERRY_ALLOW_UNIMPLEMENTED=1 pretty run

/usr/bin/x86_64-linux-gnu-ld.bfd: network_database_ts.o: in function `perry_closure_network_database_ts__313': perry_llvm_30672_1778555008884757367_19.ll:(.text+0x3099e): undefined reference to `default' /usr/bin/x86_64-linux-gnu-ld.bfd: network_database_ts.o: in function `perry_closure_network_database_ts__405': perry_llvm_30672_1778555008884757367_19.ll:(.text+0x49bce): undefined reference to `default' /usr/bin/x86_64-linux-gnu-ld.bfd: network_routes_account_ts.o: in function `perry_closure_network_routes_account_ts__19': perry_llvm_30672_1778555008811092836_16.ll:(.text+0x215): undefined reference to `js_axios_response_data_parsed' /usr/bin/x86_64-linux-gnu-ld.bfd: perry_llvm_30672_1778555008811092836_16.ll:(.text+0x22a): undefined reference to `js_axios_response_data_parsed' /usr/bin/x86_64-linux-gnu-ld.bfd: perry_llvm_30672_1778555008811092836_16.ll:(.text+0x26a): undefined reference to `js_axios_response_data_parsed' collect2: error: ld returned 1 exit status Error: Linking failed

the symbol "perry_closure_network_database_ts__313" and "perry_closure_network_database_ts__405" are not found in the HIR

database_ts.txt
hir.txt

[proggeramlug]

Fixed in #734 (will ship in v0.5.892).

The literal default symbol came from a default import resolving to a module Perry couldn't compile natively (no perry-stdlib binding, not in compilePackages). In your repo, import sanitizeHtml from 'sanitize-html' (and similar) was the trigger.

Chain:

1. HIR registers default-import bindings with the original-name sentinel "default" (lower.rs:3727).
2. Identifier lookup resolved the local to Expr::ExternFuncRef { name: "default" }.
3. The codegen call path fell through every special case and the import_function_prefixes map (which only contains NativeCompiled imports — V8-fallback JsModule imports have no entry).
4. The fallthrough emitted call double @default(...) → linker can't resolve default.

The fix routes bare-"default" ExternFuncRef calls (no import_function_prefixes entry) to a new runtime stub js_unresolved_default_call that returns undefined and prints a one-shot diagnostic on first call:

perry: called a default-imported binding from an unresolved module (returns undefined). The module's default export was not found in perry-stdlib or perry.compilePackages — run `perry --print-api-manifest` to see what's supported.
result: undefined

So the binary will now link and run — but sanitizeHtml(content) etc. will return undefined because Perry doesn't yet have a native binding for those packages. You'll need to either find perry-stdlib-supported alternatives or add the package to perry.compilePackages (which works for packages whose source Perry can compile).

The separate js_axios_response_data_parsed issue you hit when setting PERRY_ALLOW_UNIMPLEMENTED=1 is a different bug (axios extension lib not being linked when needed) — please open a separate issue for that with a small repro and I'll take a look.

A new version with the fix will be released shortly.