WuTheFWasThat / vimflowy

An open source productivity tool drawing inspiration from workflowy and vim
https://www.wuthejeff.com/vimflowy
MIT License
1.6k stars 111 forks source link

Assets does not build #357

Closed benoitjpnet closed 3 years ago

benoitjpnet commented 3 years ago

npm run build or npm run build -- --outdir /home/note/vimflowy/static/build/ result in nothing getting built.

Any ideas where to look for debuging?


npm run build

> vimflowy@0.0.1 build /home/note/vimflowy
> ts-node src/server/build.ts

ℹ 「atl」: Using typescript@3.1.6 from typescript
ℹ 「atl」: Using tsconfig.json from /home/note/vimflowy/tsconfig.json
ℹ 「atl」: Checking started in a separate process...
ℹ 「atl」: Time: 2118ms

npm run startprod -- --db sqlite --dbfolder /home/note/db --password xxx
> vimflowy@0.0.1 startprod /home/note/vimflowy
> ts-node src/server/prod.ts "--db" "sqlite" "--dbfolder" "/home/note/db" "--password" "xxx"

        No assets found at /home/note/vimflowy/static/build/!
        Try running `npm run build -- --outdir /home/note/vimflowy/static/build/` first.
        Or specify where they should be found with --staticDir $somedir.
WuTheFWasThat commented 3 years ago

what versions of node and npm do you have?

node --version
v13.9.0

npm --version
6.13.7
benoitjpnet commented 3 years ago
root@note:~# node --version
v14.15.3
root@note:~# npm --version
6.14.9
WuTheFWasThat commented 3 years ago

maybe try downgrading node, not sure. I recommend nvm for managing multiple versions

benoitjpnet commented 3 years ago

Is there any way to have a verbose mode enabled?

WuTheFWasThat commented 3 years ago

ok, i struggled for awhile with this problem. I'm not sure how to track it down but something changed about the behavior of my webpack configuration

WuTheFWasThat commented 3 years ago

https://github.com/WuTheFWasThat/vimflowy/issues/358 was probably related

WuTheFWasThat commented 3 years ago

@benpro could you try again on master?

WuTheFWasThat commented 3 years ago

feel free to reopen if not solved

benoitjpnet commented 3 years ago

Indeed fixed. Thanks!