search

SAFE-Stack / SAFE-Nightwatch

Demo of SAFE-Stack applied to React Native for cross platform native mobile apps
The Unlicense
157 stars 29 forks source link

fable-splitter package not installed #56

Closed richardjharding closed 6 years ago

richardjharding commented 6 years ago

I've cloned this out on two diff windows machines with the same result

after running build.cmd debug

The build fails at the CompileForTest target

The cause is that the fable-splitter package has not been installed

Finished Target: Restore
Starting Target: SetReleaseNotes (==> Restore)
Finished Target: SetReleaseNotes
Starting Target: SetVersionAndroid (==> SetReleaseNotes)
Finished Target: SetVersionAndroid
Starting Target: SetVersion (==> SetVersionAndroid)
Finished Target: SetVersion
Starting Target: CompileForTest (==> SetVersion)
C:\Users\richa\AppData\Local\dotnetcore\dotnet.exe  fable npm-run compile-for-test
Fable (1.3.8) daemon started on port 61225
CWD: D:\Source\Repos\SAFE-Nightwatch
cmd /C npm run compile-for-test

> nightwatch@1.0.0 compile-for-test D:\Source\Repos\SAFE-Nightwatch
> fable-splitter -c splitter.config.js --define TEST

'fable-splitter' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! nightwatch@1.0.0 compile-for-test: `fable-splitter -c splitter.config.js --define TEST`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nightwatch@1.0.0 compile-for-test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\richa\AppData\Roaming\npm-cache\_logs\2018-03-22T16_41_28_382Z-debug.log
Closing Fable daemon...
Running build failed.

This is confirmed by examining the node_modules folder - in fact

I've tried both yarn install and npm install - neither will install the dependency in this project

If I create a new folder , npm init and npm install --save-dev fable-splitter

then it is installed and the correct .cmd file created in node_modules/.bin

As a result I don't think its my system but something in this config ?

Any suggestions on what I can check ?

I'm running node 6.11.0 npm 5.5.1

I see no errors during the yarn install thats run as part of the FAKE target

I'm able to create a new react-native app (non fable) and run ok I'm also able to create a new fable web app - eg the Fable-elmish-react-demo app - but that doesn't use fable-splitter

forki commented 6 years ago

Maybe this was during nuget outtage?

Richard Harding notifications@github.com schrieb am Do., 22. März 2018, 17:46:

I've cloned this out on two diff windows machines with the same result

after running build.cmd debug

The build fails at the CompileForTest target

The cause is that the fable-splitter package has not been installed

I've tried both yarn install and npm install - neither will install the dependency in this project

If I create a new folder , npm init and npm install --save-dev fable-splitter

then it is installed and the correct .cmd file created in node_modules/.bin

As a result I don't think its my system but something in this config ?

Any suggestions on what I can check ?

I'm running node 6.11.0 npm 5.5.1

I see no errors during the yarn install thats run as part of the FAKE target

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SAFE-Stack/SAFE-Nightwatch/issues/56, or mute the thread https://github.com/notifications/unsubscribe-auth/AADgNCclIAdmbr1aiIa1CWtabEAsP7awks5tg9VegaJpZM4S3aIt .

richardjharding commented 6 years ago

not sure - I've deleted node_modules and re-ran build.cmd and got the same result - I was still able to create a new folder and npm install fable-splitter in that - just doesn't get installed in this file structure during build can't really see why

forki commented 6 years ago

Delete packages folder as well

Richard Harding notifications@github.com schrieb am Do., 22. März 2018, 18:32:

not sure - I've deleted node_modules and re-ran build.cmd and got the same result - I was still able to create a new folder and npm install fable-splitter in that - just doesn't get installed in this file structure during build can't really see why

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/SAFE-Stack/SAFE-Nightwatch/issues/56#issuecomment-375392742, or mute the thread https://github.com/notifications/unsubscribe-auth/AADgNGqKHnbDfVyHETm89LBibJtIY1Vdks5tg-AfgaJpZM4S3aIt .

richardjharding commented 6 years ago

yep that sorted it - what am I missing - whats the connection between nuget packages and npm fable-splitter?

forki commented 6 years ago

It's not a npm package AFAIK.

Richard Harding notifications@github.com schrieb am Do., 22. März 2018, 23:15:

yep that sorted it - what am I missing - whats the connection between nuget packages and npm fable-splitter?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/SAFE-Stack/SAFE-Nightwatch/issues/56#issuecomment-375475367, or mute the thread https://github.com/notifications/unsubscribe-auth/AADgNA5NzJRHCqKsD1EN0bUHlNyFwI-pks5thCKNgaJpZM4S3aIt .

richardjharding commented 6 years ago

odd - its listed in package.json and gets added to node_modules and node_modules/.bin but cloning out again fresh worked - no idea

forki commented 6 years ago

Ok then I was wrong about it. But I still assume it was the outtage. Maybe some other fable components were missing

Richard Harding notifications@github.com schrieb am Fr., 23. März 2018, 10:27:

Closed #56 https://github.com/SAFE-Stack/SAFE-Nightwatch/issues/56.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/SAFE-Stack/SAFE-Nightwatch/issues/56#event-1537427691, or mute the thread https://github.com/notifications/unsubscribe-auth/AADgNJL_tQ4wccZKDLrONK3X6MYN_99zks5thL_wgaJpZM4S3aIt .