Open vasco3 opened 5 months ago
Will have a look into this.
Can you run it with a backtrace with any chance? RUST_BACKTRACE=1
?
@vasco3 - Made this optional for now: https://github.com/teamwalnut/rewatch/releases/tag/v1.0.6 -- Release is building.
But - would love to work on fixing this. It looks to me like the path of the package it's trying to resolve is a sub path of another package. Are you able to build Rewatch from source? Ie - If I prepare a branch for you with some debug statements, would you be able to compile it and run it on your repo so we get some debug information?
RUST_BACKTRACE=1
like this? (v1.0.6)
Yeah, could be that this doesn't work in release mode. But let's try:
pnpm rewatch clean .
- clean stateRUST_BACKTRACE=1 pnpm rewatch build .
(this should then spawn the error and hopefully give us a backtrace).If it doesn't I'll try and prepare a build for you that you can install which will have some more debug info.
@rolandpeelen looks like now its working fine? v1.0.6
Hey! Yes, we made them optional. Sorry, should have included the tag. So;
pnpm rewatch clean . - clean state
RUST_BACKTRACE=1 pnpm rewatch --create-sourcedirs true build .
@rolandpeelen here is the result
running with full
Awesome. Thank you! Ok. there is not that much info there unfortunately. Would you happen to have you have a small public github repo that reproduces this issue?
Alternatively, I can build you a version of Rewatch that does some more logging. But not sure when I can get to that
@rolandpeelen yeah I'll put together a repro repo soon
@rolandpeelen good news,
The sourcedirs error happens when I add @rescript/react
here is the minimal repo https://github.com/vasco3/rewatch-pnpm
run rewatch clean and rewatch watch. Then i see the following error
I rolled back and it works fine again.
dependencies
"@rescript/react": "^0.12.1",
"rescript": "11.1.0",