Type Error with Example
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- nodejs, webpack
- Domain
- build-system
Research direction
Start by generating the vanilla project with the default options and running npm run start to reproduce the res.getHeader error. Inspect webpack.serve.config.js and the webpack-dev-middleware stack shown in the report; done means the generated example project starts and displays the example input component.
Written by the indexing model from the issue text.
Description
Currently I am unable to run the vanilla boilerplate without any changes. I run cookiecutter with all default options except for the author name and email address. If I run "npm run start" on the newly generated project, it should display the example input component. However, I get the following error:
TypeError: res.getHeader is not a function
at processRequest (C:\source\my_dash_component\node_modules\webpack-dev-middleware\lib\middleware.js:82:18)
at cbs.forEach (C:\source\my_dash_component\node_modules\webpack-dev-middleware\lib\context.js:52:9)
at Array.forEach ()
at process.nextTick (C:\source\my_dash_component\node_modules\webpack-dev-middleware\lib\context.js:51:11)
at process._tickCallback (internal/process/next_tick.js:61:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my_dash_component@0.0.1 start: webpack-serve ./webpack.serve.config.js --open
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my_dash_component@0.0.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\myUser\AppData\Roaming\npm-cache_logs\2019-03-13T10_04_36_318Z-debug.log
I assume there's something wrong with the dependencies. However, I am unable to resolve it myself.
- Dominant language
- Python
- Stars
- 294
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from plotly/dash-component-boilerplate
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
plotly/dash-component-boilerplate#173 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
plotly/dash-component-boilerplate#170 · 1 comment ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
plotly/dash-component-boilerplate#166 · 1 reaction ·
-
Running build Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
All issues in plotly/dash-component-boilerplate
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·