It can not start the server with nuekit 0.5.3, but works with nue 0.4.3

[xiejx618]

OS : windows 11 23H2（22631.3374）
bun：1.1.2

E:\admin-dashboard>bun install nuekit@0.4.3 --global
bun add v1.1.2 (c8d072c2)

installed nuekit@0.4.3 with binaries:

• nue

1 package installed [31.00ms]

E:\admin-dashboard>nue

✓ Nue 0.4.3 • Bun 1.1.2
✓ Initialize ./.dist/dev: ••••••••••✓ Serving site from ./.dist/dev
✓ Building site to: ./.dist/dev

✓ Single-page apps 1
index.html

Time taken: 13ms

✓ http://localhost:8080/
^C
E:\admin-dashboard>bun uninstall nuekit --global
bun remove v1.1.2 (c8d072c2)

• nuekit
  1 package removed [15.00ms]

E:\admin-dashboard>bun install nuekit --global
bun add v1.1.2 (c8d072c2)

installed nuekit@0.5.3 with binaries:

• nue

1 package installed [3.32s]

E:\admin-dashboard>nue

✓ Nue 0.5.3 • Bun 1.1.2
✓ Initialize ./.dist/dev: ••••••••••
✓ Building site to: ./.dist/dev

Time taken: 1ms

E:\admin-dashboard>

[kzt-wt]

I'm facing the same problem.

[nobkd]

@kzt-wt are you also using bun on windows?

I'll test it on Windows later today / when I find the time. Then, we'll see, if there is some Windows related code / bun problems :)

[kzt-wt]

Yes
I'm using bun on Windows.

[nobkd]

I was able to reproduce this unexpected behavior. Will have to check since which change this happens.
I also haven't checked yet, if it also happens for node on windows... (sorry for the slow progress, )

EDIT:
Happens for both node (with env shebang edited to node) and bun since nuekit 0.5.2
So 0.5.1 / 0.5.0 work fine, but some resources are not converted / found on serve I think...

[nobkd]

I made a git bisect and the first bad commit is 6a7464b (Simplified stats command), even when fixing the doubled function fmt and the wrong imports.
Will investigate further.

[nobkd]

Found the problem:

nue/packages/nuekit/src/cli.js

Lines 106 to 107 in 6a7464b

	// build
	else if (push || args.paths[0] || cmd == 'build') {

args.paths contains the path to the cli.js file on Windows, because it wasn't filtered.

Important

This issue is already fixed with #239, but not released yet...
Soo: Duplicate of #179

I will try making it more robust, but that's it...