• Robert Knight's avatar
    Avoid creating unnecessary production build when running `make dev` · 20b558f4
    Robert Knight authored
    `make dev` would unnecessarily create a production build before starting
    the development server if `package.json` or `yarn.lock` had been touched
    since the previous run of `make dev`. This was happening because `make dev`
    had a dependency on `build/manifest.json`, which triggers a production
    build, rather than `node_modules/.uptodate`, which just runs `yarn
    install`. I can't remember the historical reason why it was this way, but it
    doesn't make sense any more.
    
    Fix this by changing `make dev` to only depend on `node_modules/` being
    up to date before starting the dev server.
    20b558f4
Name
Last commit
Last update
.github Loading commit data...
bin Loading commit data...
dev-server Loading commit data...
docs Loading commit data...
embedding-examples Loading commit data...
images Loading commit data...
scripts Loading commit data...
src Loading commit data...
.babelrc Loading commit data...
.dockerignore Loading commit data...
.eslintignore Loading commit data...
.eslintrc Loading commit data...
.gitignore Loading commit data...
.npmignore Loading commit data...
.npmrc Loading commit data...
.prettierignore Loading commit data...
.prettierrc Loading commit data...
.python-version Loading commit data...
CODE_OF_CONDUCT Loading commit data...
Dockerfile Loading commit data...
Jenkinsfile Loading commit data...
LICENSE Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
codecov.yml Loading commit data...
gulpfile.js Loading commit data...
package.json Loading commit data...
requirements-dev.in Loading commit data...
tox.ini Loading commit data...
yarn.lock Loading commit data...