SolidStart 1.1.0 does not work with Bun

[PalmDevs]

What version of Bun is running?

1.2.7+5c0fa6dc2

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What steps can reproduce the bug?

1. bun create solid
2. Create a new SolidStart project with the bare template and TypeScript
3. cd into the directory and install dependencies
4. bun --bun dev
5. Once the server starts, visit the site (eg. localhost:3000)
6. Notice the errors

What is the expected behavior?

SolidStart works correctly with Bun, since it works using Node. Visiting the site should not cause any errors.

What do you see instead?

9:45:36 PM [vite] Internal server error: File URL path must be an absolute path
  Plugin: tanstack-start-directive-vite-plugin
  File: /@solid-refresh
      at fileURLToPath (native)
      at transform (C:\Users\Palm\Desktop\solid\node_modules\@tanstack\directive-functions-plugin\dist\esm\index.js:19:12)
      at <anonymous> (C:\Users\Palm\Desktop\solid\node_modules\vite\dist\node\chunks\dep-Pj_jxEzN.js:47681:19)
      at processTicksAndRejections (native) (x2)
9:45:36 PM [vite] (client) Pre-transform error: File URL path must be an absolute path
  Plugin: tanstack-start-directive-vite-plugin
  File: /@solid-refresh

Additional information

SolidStart issue opened here: solidjs/solid-start#1800

[birkskyum]

Hmm, can't repro this. What operation system are you using?

[PalmDevs]

Microsoft Windows NT 10.0.26100.0 x64, or Windows 11.

[birkskyum]

I'm on mac. Could be a platform specific

[MauruschatM]

For me, it also doesn't work on Windows 10 using “bunx --bun vinxi dev”
Now I use just "vinxi dev" on Windows and deploying it on linux with nixpack “bunx --bun vinxi build”

[RiskyMH]

Looks like the same issue as #20403 - it has a similar stack trace with pathToFileURL also:

ERROR  [request error] [unhandled] [GET] http://localhost:3000/                                                             06:40:55

ℹ Error: File URL path must be an absolute path

 ⁃ at directRequest (E:/test/test-nuxt-unocss/node_modules/vite-node/dist/client.mjs:280:22)

   275 ┃                if (transformed == null) throw new Error([vite-node] Failed to load "${id}" imported from ${callstack[callstack.length - 2]});
   276 ┃                const { Object, Reflect, Symbol } = this.getContextPrimitives();
   277 ┃                const modulePath = cleanUrl(moduleId);
   278 ┃                // disambiguate the <UNIT>:/ on windows: see nodejs/node#31710
   279 ┃                const href = pathToFileURL(modulePath).href;
 ❯ 280 ┃                const filename = fileURLToPath(href);
   281 ┃                const dirname = dirname(filename);
   282 ┃                const meta = {
   283 ┃                        url: href,
   284 ┃                        env,
   285 ┃                        filename: filename,

 ⁃ at processTicksAndRejections (native:7:39)

[CAUSE]
TypeError {
  message: 'File URL path must be an absolute path',
  originalLine: 126,
  originalColumn: 168,
  line: 280,
  column: 22,
  sourceURL: 'E:\test\test-nuxt-unocss\node_modules\vite-node\dist\client.mjs',
  stack: 'File URL path must be an absolute path\n' +
  'at directRequest (E:/test/test-nuxt-unocss/node_modules/vite-node/dist/client.mjs:280:22)\n' +
  '    at processTicksAndRejections (native:7:39)',
}

[RiskyMH]

bun/src/bun.js/bindings/BunObject.cpp

Lines 688 to 696 in 28006d0

	#if OS(WINDOWS)
	if (!isAbsolutePath(fileSystemPath)) {
	Bun::ERR::INVALID_FILE_URL_PATH(scope, globalObject, "must be an absolute path"_s);
	return {};
	}
	#endif
	return JSC::JSValue::encode(JSC::jsString(vm, fileSystemPath));
	}

related code (and why its windows only)

---

And works without #8442 (i.e version before with 1.2.0).

Considering how it was fixing node compatibility (on error that only shows on windows), I'd assume there is some plugin that vite/solid is hooking into so node doesn't resolve it fully like this, whereas bun just gets confused earlier on.

[RiskyMH]

(also note that somehow bun runtime doesn't create all the needed files in bun --bun create solid)