You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{SANDBOX} [17:39:43] /src/types/hellojs [master] > retyped index.d.ts
module.js:549
throw err;
^
Error: Cannot find module './js/src/compiler'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/nick/.npm-global/lib/node_modules/reasonably-typed/lib/index.js:2:17)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
The text was updated successfully, but these errors were encountered:
This is just a matter of not having shipped the JS artifacts, right? For instance, I can fix this by running bsb -make-world in the install directory (not that that's the solution :P). I'm new at NPM, but is this just fixed by having a prepublishOnly hook that produces the JS artifacts? On the other hand (I was curious and browsed around) it looks like reason-react commits their artifacts to source. Does a more experienced NPM person know what to do?
2.0 isn't ready yet, sorry! It still needs a ton of work to handle most cases. The main driving factor for 2.0 is to be the backing library for styled-scss, and it's super not ready for CLI usage
@rrdelaney please provide separate npm tag if you are publishing beta version like npm publish --tag next
But anyway if you are publishing it to npm it must be ready for usage.
The
retyped
command crashes when installing the 2.0.0 releases from npm.The text was updated successfully, but these errors were encountered: