+2I’ve been banging my head against a wall here. `block run` appears to run successfully but the webserver isn’t returning content and instead is returning a 404. A `block release` works successfully and I can see the `Hello World` in my extension. It’s running on port 9000 and it’s listening cause I get a response, it just doesn’t have any content.
Any ideas?
+25+2Thanks for sharing. Sounds like mine is not an isolated case but write/release/debug isn’t really a workflow I’m going to pursue.
Thanks again.
+2I was wrong about the webpack dev server .. digging in more, it appears to be express not responding. Not sure how to amend the title or change this whatsoever but if anyone stumbles on it … my issue seems to be with express. Still digging.
+2About to walk away from this but in case anyone stumbles upon this and feels like a hero I figured I’d mention that both the upstream and downstream servers respond for requests to `/bundle.js` (although it’s returned as a document) but none of the other assumed endpoints like `/ping` or even `/index.js` which is sitting in the `.tmp` directory return data and instead send a 404.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
