Error during npm run build

[ArnoBuschmann]

After I npm installed everything, when running npm run build, this error gets thrown:

Error: Cannot find module 'rxmarbles/app-view' from 'mylocalpath/rxmarbles/ignore/es5src'

When running npm run preinstall and then npm run build again, I get this error:

Error: Cannot find module 'cyclejs' from 'mylocalpath/rxmarbles/ignore/es5src'

[desnor]

I encountered a similar issue when trying to start up the app:

> rxmarbles@1.4.1 preinstall .../side-projects/rxmarbles
> rm -rf build && rm -rf node_modules && mkdir -p ignore/es5src

> rxmarbles@1.4.1 postinstall .../side-projects/rxmarbles
> ln -s ../ignore/es5src node_modules/rxmarbles && ln -s ../package.json node_modules/package.json

ln: node_modules/rxmarbles: No such file or directory

So I tried it after removing the rm -rf build && rm -rf node_modules part of the preinstall script because it wasn't saving the node_modules folder. This then installed fine. But after running npm run build I then got this error:

> browserify -e ignore/es5src/app.js --outfile dist/js/app.js

Error: Cannot find module '@cycle/core/node_modules/rx/package.json' from '.../side-projects/rxmarbles/node_modules/rxmarbles'

Is that an issue with the symbolic linking? I'm not familiar with how that is supposed to work so while I'd like to try and resolve it (I'm really keen to find a way to contribute to the project) I might need a few pointers for how to approach this. Maybe it's something else beyong my knowledge that's causing the issue however.

Anyway if anyone has a suggestion for how I could approach getting this going I would appreciate any tips. I found playing with the marbles really helpful for learning about observable streams so I really want to help out.

[pbadenski]

Not sure what a "correct" solution for this is, but you can brute-force it by running "npm install" from within 'node_modules/@cycle' directory.

[desnor]

Thanks for that @pbadenski - I had to also run npm install from within the node_modules/@cycle/core directory too - but it's all going now. I also updated my node version but I don't think that would have made a difference.