vaadin/base-starter-connect

`npm run start:webpack` does not work as described in README

Open

#106 opened on Sep 3, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (2 forks)auto 404
buggood first issue

Repository metrics

Stars
 (9 stars)
PR merge metrics
 (PR metrics pending)

Description

hey, I noticed that the Vaadin Connect starter app (https://github.com/vaadin/base-starter-connect) gives an error npm ERR! missing script: start:webpack if you try to run the processes separately with npm run start:webpack.

It looks like the README is out of date. You either have to run npm start (which runs webpack, backend and apibrowser) or write your own start:webpack script if you want to run only webpack

The way to do that manually would be ./node_modules/.bin/webpack --mode development --watch

DoD:

  • README contains correct instructions on how to start only the front-end in the dev mode
  • (it may require adding a new script into @vaadin/connect-scripts)

Contributor guide

Research direction
Inspect the README instructions for starting the frontend, run `npm run start:webpack` to confirm it fails, and check the `scripts` section of `package.json` in the root and in the `@vaadin/connect scripts` package. Then update the README to reflect the correct command (either `npm start` or the newly added script).
Tech stack
javascriptnodejs
Domain
frontendbuild system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gitnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85