`npm start` does not work for me

[Akronix]

I've followed the instructions written in the README.md file for installing and setting up the development environment.

However, when I do npm start my browser page is black and I only see an error in the console saying:

output.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)

Here is the screenshot:

[valentijnnieman]

@T4rk1n Could you take a look at this? I think I just copied the webpack config from what you did at dash-component-boilerplate.

[T4rk1n]

I'd just delete the script, there's no point in running those demos, they don't run the dash-renderer so you don't get setProps and all that jazz. You're always better off running a usage.py.

[Akronix]

I agree with @T4rk1n. If it doesn't run dash-renderer it won't be of any use to me for this repo.

[valentijnnieman]

I think there's still value in being able to run just the React code, without having to use Dash. If, for example, all you are doing is changing some UI code, it is faster to just run the JS code and not bother with any Python at that point. In any case, if we have a demo app, as we do in demo/Demo.react.js, we should support that and make sure that it works, or remove it entirely (including the webpack configs).

[Akronix]

Ups, I lost the context and I did a mistake. I thought that this was dash-renderer repo when I read that comment and I responded accordingly 😅 .

For dash core components it is useful to have a working pure JS Demo, because I want to test the React components in pure JS before to do the whole python binding. Actually, this is why I opened the issue: I wanted to test the input component in react before to make any further changes.
So yes, a working npm start script would be nice.

[valentijnnieman]

Similarly happening in dash-component-boilerplate, here #27

[T4rk1n]

It was resolved in plotly/dash-component-boilerplate#28