fix: preserve bare specifiers for subpath and undeclared external imports in rolldown build (#540)

The rolldown external config used exact string matching, which failed to
match dependency subpath imports (e.g. `@noble/hashes/sha2.js` did not
match `@noble/hashes`). This caused the build to resolve these imports
to relative `node_modules` paths, breaking consumers at runtime.

Author: aorumbayev

package-lock.json

@@ -127,6 +127,8 @@
     "esbuild": "0.25.0"
   },
   "dependencies": {
+    "@algorandfoundation/xhd-wallet-api": "2.0.0-canary.1",
+    "@noble/ed25519": "^3.0.0",
     "@noble/hashes": "^2.0.1",
     "algorand-msgpack": "^1.1.0",
     "buffer": "^6.0.3",

package.json

@@ -9,7 +9,11 @@ type StringOrRegExp = string | RegExp
 const nodeBuiltins = builtinModules.flatMap((m) => [m, `node:${m}`])
 
 export default function createConfig(externalDependencies: StringOrRegExp[], input: string[] = ['src/index.ts']): typeof config {
-  const external = Array.from(new Set([...nodeBuiltins, ...Object.keys(workspacePkg.dependencies || {}), ...externalDependencies]))
+  const external: StringOrRegExp[] = [
+    ...nodeBuiltins,
+    ...[...Object.keys(workspacePkg.dependencies || {}), ...externalDependencies]
+      .map(dep => typeof dep === 'string' ? new RegExp(`^${dep}($|\\/|\\\\)`) : dep),
+  ]
 
   const resolvedInput = input.flatMap((pattern) => {
     // If it contains glob characters or negations, resolve with fast-glob