Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

gulpfile.babel.js blocking grommet-toolbox "gulp dev" task

See original GitHub issue

The default “gulp dev” task in gulpfile.babel.js is blocking the groomet-toolbox “gulp dev” task.

gulp.task('dev', () =>
  console.error(
    'Running "gulp dev" at Grommet root folder is not supported. If you want to start the website, run "gulp dev" at docs folder'
  )
);

Issue Analytics

State:
Created 7 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

alansouzaticommented, Apr 18, 2016

correct, we need to update the message. Can you craft a Pull Request to update the console message properly?

The grommet website has been moved to a separate repo:

https://github.com/grommet/grommet-docs

To test grommet components I usually use the website, so I’m glad you are going in the same direction.

If you clone grommet-docs at the same workspace as you have grommet, as in:

  /grommet-workspace
    - /grommet
    - /grommet-docs

Inside grommet-docs you can run gulp dev --useAlias. This command will start the website pointing to your grommet core instead of using the one from node_modules.

Hopefully this helps, the configuration to make this work is in here:

https://github.com/grommet/grommet-docs/blob/master/grommet-toolbox.config.js#L58

and here

https://github.com/grommet/grommet-docs/blob/master/gulpfile.babel.js#L35

0reactions

alansouzaticommented, Apr 19, 2016

Yeah I can experience the issue with hot reloading as well.