Browsers Launched Through VSCode Never Load React Sarted With react-scripts start

By -

Until last night, I used to just hit F5 in VS code and debug my react app (typescript, run with PORT=4200 BROWSER=none react-scripts start by way of npm start).

App: https://github.com/micahg/ntt

I'm physically running NPM in wsl2 and the browsers access it via localhost on windows. Hasn't been an issue this far...

Now when I launch the frontend from code, the browser launches but never loads the page. I can reproduce this across edge or chrome, using a launch config that looks like this:

        {
            "type": "chrome",
            "request": "launch",
            "name": "Launch against localhost",
            "url": "http://localhost:4200",
            "webRoot": "${workspaceFolder}",
        }

If I refresh/reload in browser and look at the traffic, it looks like I get a response to GET / (http 200) but there is no body. The tab's loading animation is spinning around too so it seems like its waiting for a response to the call to http://localhost:4200/ but it never comes. Page is blank -- i think maybe I really am not getting a response in THAT browser.

What is really confusing is that it seems (somehow) tied to vscode. If I hit the same url outside of WSL through curl, chrome, firefox, edge, netscape navigator, etc started through normal means everything is fine. Anything launched within code... never actually fetches the response body.

I realize this post might be a little light on detail but I'm not really sure what info would help... I'm about to get wireshark out over here just to prove I'm not insane, but if anyone has any suggestions I'd take them as this is so bizarre (or I've overlooked something monumentally).

I did have a look at https://create-react-app.dev/docs/advanced-configuration/ but there doesn't seem to be a verbose mode or traffic log or anything.

Thanks in advance,



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more