[BUG] Build Successfully, but the blazebuild folder is emptied after the build
Closed this issue · 13 comments
BUILD SUCCESSFUL in 5m 52.17s
7 actionable tasks: 7 executed
PS C:\Users\Cjeck\sudobot> ./blazew run -- -- -u -g
warn Node.js global version mismatch: required 22.4.1, found 20.15.1
info Installing BlazeBuild dependencies...
[0.00ms] ".env"
bun install v1.1.20 (ae194892)
$ husky && rm -fr node_modules/blazebuild && node -e "const { symlinkSync } = require('fs'); const path = require('path'); symlinkSync(path.join(process.cwd(), 'blazebuild'), path.join(process.cwd(), 'node_modules/blazebuild'), 'dir');"
Checked 766 installs across 811 packages (no changes) [12.72s]
error: Failed to find entry file for execution in directory: C:\Users\Cjeck\sudobot\blazebuild (Path: C:\Users\Cjeck\sudobot\blazebuild/src/main/typescript/cli.ts)
PS C:\Users\Cjeck\sudobot>
this is definitely a weird issue, i take it that this would only happen on windows, @virtual-designer maybe you can figure this out
this is definitely a weird issue, i take it that this would only happen on windows, @virtual-designer maybe you can figure this out
i'll try to use wsl
and see if it work
i'll try to use wsl
alright, let me know how that goes
i'll try to use wsl
alright, let me know how that goes
nothing happens LOL
nothing happens LOL
try run it again maybe? it did say installing bun version 1.1.20
Have you updated your instance to latest? I've made some changes to BlazeBuild too.
this is definitely a weird issue, i take it that this would only happen on windows, @virtual-designer maybe you can figure this out
Not anymore cause Windows is supported now.
Not anymore cause Windows is supported now.
yeah ive heard that windows is supported, but that is definitely a weird issue that happened
@virtual-designer I need help with the tabs, they're not working
@virtual-designer I need help with the tabs, they're not working
is this on the dashboard? if so, i dont think the dashboard is fully ready for production use yet as its still being worked on iirc
@virtual-designer I need help with the tabs, they're not working
is this on the dashboard? if so, i dont think the dashboard is fully ready for production use yet as its still being worked on iirc
aight
@virtual-designer I need help with the tabs, they're not working
is this on the dashboard? if so, i dont think the dashboard is fully ready for production use yet as its still being worked on iirc
aight
Yeah, I've said this before too.
BUILD SUCCESSFUL in 5m 52.17s 7 actionable tasks: 7 executed
PS C:\Users\Cjeck\sudobot> ./blazew run -- -- -u -g warn Node.js global version mismatch: required 22.4.1, found 20.15.1 info Installing BlazeBuild dependencies... [0.00ms] ".env" bun install v1.1.20 (ae194892)
$ husky && rm -fr node_modules/blazebuild && node -e "const { symlinkSync } = require('fs'); const path = require('path'); symlinkSync(path.join(process.cwd(), 'blazebuild'), path.join(process.cwd(), 'node_modules/blazebuild'), 'dir');"
Checked 766 installs across 811 packages (no changes) [12.72s] error: Failed to find entry file for execution in directory: C:\Users\Cjeck\sudobot\blazebuild (Path: C:\Users\Cjeck\sudobot\blazebuild/src/main/typescript/cli.ts) PS C:\Users\Cjeck\sudobot>
As for the explanation on why this issue had occurred, it was because the inline shell command 1that the postinstall script runs each time after dependency changes. The inline rm command caused this issue.
I forgot to add checks and make sure to not remove the symbolic link recursively, which behaves differently in Windows systems, removing the path which the link points to. Comparing this to a Linux/Unix based system, it would rather just remove the symbolic link and not modify the original path.
This issue has been addressed in the latest releases.
I'll be closing this issue. Feel free to create a new one if you have any further issues.