[Bug?]: SolidStart 1.1.0 does not work with Bun

[PalmDevs]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

Using the bare template, the dev server starts, but going to the site causes server errors:

[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-project\node_modules\@tanstack\directive-functions-plugin\dist\esm\index.js:19:12)
      at <anonymous> (C:\Users\Palm\Desktop\solid-project\node_modules\vite\dist\node\chunks\dep-CfG9u7Cn.js:47598:19)
      at processTicksAndRejections (native) (x4)

Expected behavior 🤔

Visiting the site should not cause any server errors.

Steps to reproduce 🕹

Steps:

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

Context 🔦

I am trying to use SolidStart with Bun. It has worked great previously, but updating to 1.1.0 causes this issue.

Your environment 🌎

System:
  OS: Microsoft Windows [Version 10.0.26100.3037]
  CPU: x86_64 (6 cores, 12 processors)
Binaries:
  Bun: 1.2.2
npmPackages:
  @solidjs/start@1.1.0
  solid-js@1.9.4
  vinxi@0.5.3

[phong-phuong]

Strange, I just tested creating a new project, and it works for me.

OS is alsoWindows, tested with older (1.1.x version of Bun) and latest version of bun (1.2.x).

[phong-phuong]

Try solidstart 1.1.1, just came out a day ago which I used in the test.

[PalmDevs]

Nope, using SolidStart 1.1.1 didn't fix the issue. Did you start the dev server with --bun?

[PalmDevs]

[phong-phuong]

Ok I missed that important detail bun --bun dev, and didn't know that option existed, and is very useful.
When I use bun --dev dev, it does indeed fail with the same errors as yours.

[birkskyum]

I can't repro this, on macos, with the bun --bun dev

@PalmDevs are you able to repro this in a stackblitz?

@phong-phuong , what's your environment? can this be a windows-only issue?

[phong-phuong]

@birkskyum OS: Windows 11

[birkskyum]

@phong-phuong , and this works if you run npm run dev instead, right?

[phong-phuong]

@birkskyum That is correct. Only the bun --bun dev command doesn't run successfully on Windows as described in this issue.

[birkskyum]

Okay. Then we need this ticket opened in bun repo instead, because it appear this is not an issue on our side, and bun has a mantra that "if it works in node it should work in bun."

[MarByteBeep]

Experiencing the same issue. Has this been forwarded to the Bun dev? If so, could someone reference the issue here?