pastilhasandClaude Opus 5
79fbfee5fb
The extraction typechecked from day one and had never been built. It took five attempts, each failing further along, and every cause was the same shape: something the shared node_modules or the monorepo's layout supplied without anyone declaring it. 1. The config plugin had the monorepo's geometry written into it — ../../../packages/officer-net/ios/libs, correct from apps/<name>/ios and meaningless from a repo root. It reported a path belonging to neither repo. Now derived from the plugin's own location with path.relative, so it is right wherever the module sits. 2. That fix appeared to do nothing, because officer-net was a dependency and bun COPIES those. Prebuild ran a week-old copy while the source was edited — a clean edit and a stale build, the same shadow-copy trap that cost a night in the monorepo. Making it a workspace turns node_modules/officer-net into a symlink. 3. @babel/plugin-transform-react-jsx was never declared by anything. It was hoisted into the monorepo by some other package, so babel-preset-expo with jsxImportSource found it by luck. 4. Same for react-native-reanimated and react-native-worklets: nativewind depends on react-native-css-interop, which lists reanimated as a PEER, whose babel plugin requires react-native-worklets/plugin. Three levels of nobody-declared-it. 5. And the self-inflicted one. Adding for (2) silently flipped bun to its isolated linker — only direct dependencies at top level, everything else symlinked into node_modules/.bun, which Metro cannot resolve. It surfaced as 'Unable to resolve module react-native-css-interop/jsx-runtime', naming a package that was installed and in the lockfile and simply not where the resolver looks. bunfig.toml now pins both properties that are needed at once: workspaces for the symlink, hoisted for the layout. Result: OffScale.app, 82 MB, with OffTailTunnel.appex at 20 MB carrying 129 Tailcore symbols — the Go core is in the extension, which is the half that matters. Not yet run on a device. It builds; that is a different claim. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
15 lines
868 B
TOML
15 lines
868 B
TOML
# React Native needs a HOISTED node_modules, and declaring `workspaces` silently changes that.
|
|
#
|
|
# `modules/officer-net` is a workspace so that node_modules/officer-net is a SYMLINK rather than a
|
|
# copy — with a `file:` dependency bun copies the package, and an edit to the config plugin then has no
|
|
# effect on the next prebuild while looking like it should. That cost three builds to find.
|
|
#
|
|
# But adding `workspaces` also flips bun to its isolated linker: only direct dependencies sit at the
|
|
# top level and everything else is symlinked into node_modules/.bun. Metro cannot resolve that — the
|
|
# failure is `Unable to resolve module react-native-css-interop/jsx-runtime`, naming a package that is
|
|
# installed, present in the lockfile, and simply not where the resolver looks.
|
|
#
|
|
# So: workspaces for the link, hoisted for the layout.
|
|
[install]
|
|
linker = "hoisted"
|