Closed alxx closed 5 years ago
Unable to reproduce the issue. Unsure if it makes a difference but here are my node and yarn versions on a macosx machine just in case.
$ node --version
v8.10.0
$ yarn --version
1.10.1
$
This also reminds me of:
Believe in those cases, it was a system specific setup that was somehow resolved but issue itself was not identified.
Hoping for some more info.
But the fact remains that during install a call is made to https://registry.npmjs.org/stdlib.themes.bootstrap.opx which returns a "not found". Try it in your browser; does it work for you?
Sure. Thanks. The https://registry.npmjs.org/stdlib.themes.bootstrap.opx doesn't work.
Wondering if there's a more direct command we can run that reproduces the issue. Helps to dig into a fix. Thinking maybe an npm or yarn command.
I tried to get closer, but couldn't. I'm not very good at the JS part; I'm in this for the Ruby side, and in fact I'm pretty annoyed that there's so much Node-related stuff that I need to wade through before I can actually start writing code. :)
Yup. Webpacker is currently used for asset compiling which uses node. Unsure if there are better tools for compiling assets at the moment. Would be interested in there are. Node land and it's ecosystem seems to be the tooling of choice of compiling assets.
This may or may not help, but if you don't need assets then consider.
jets new api --mode api
# or
jets new demo --no-webpacker
More help: jets new cli reference
Leaving open for now in case, someone is hopefully able to track down a lower-level, more direct command to dig into the issue further. Also, it may be environment specific, which makes it tricker.
Ah, that's great. I actually don't need any assets, I'm only producing JSON. The API mode should be just what I need.
Still, it'd be great if someone might be able to help with the original issue here.
Why do you think it might be environment-specific? It seems to me that Bootstrap is a pretty universal requirement.
RE: Ah, that's great. I actually don't need any assets, I'm only producing JSON. The API mode should be just what I need.
Awesome 🎉 Glad that helped. You may be interested in this article also then: Build an API with the Jets Ruby Serverless Framework
RE: Why do you think it might be environment-specific?
Mainly because wasn't able to reproduce on my machine. Also, have seen in the past that npm or yarn have updated packages or themselves in a way where default behavior changes. Then things would break depending on what versions you have. It could be what initial dotfiles were generated with those versions too. Hence sometimes reinstalling yarn or npm "fixes" the issue. It could be that with the latest version it doesn't pull from that url. Unsure 🤷🏻♂️
Thinking that's why #217 and #187 were resolved. Believe those folks ended up either blowing away their node cache or some settings and it was "fixed".
Thanks for the article! I'll certainly read it.
My Environment
Expected Behaviour
jets webpack:install
should run without errorsCurrent Behavior
The installation crashes because it can't install bootstrap, because there's actually nothing at https://registry.npmjs.org/stdlib.themes.bootstrap.opx (well, there's a JSON with the error "Not found").
Step-by-step reproduction instructions
Full error: