Skip to content
This repository has been archived by the owner on Sep 4, 2020. It is now read-only.

Hang on grommet new sample-app #1

Closed
sgelliott opened this issue Aug 10, 2016 · 2 comments
Closed

Hang on grommet new sample-app #1

sgelliott opened this issue Aug 10, 2016 · 2 comments

Comments

@sgelliott
Copy link

sgelliott commented Aug 10, 2016

Utilizing the current documentation for Grommet under "Get Going" I run into the following cases where the tasks hang without resolution.

Documentation Reference: Get Started Official Documentation

Performed the steps as mentioned in documentation:

  1. npm install -g grommet-cli -- Everything goes well
  2. 'grommet new sample-app' -- Output below...

Generating app at: ...

  1. App generation successfully completed
  2. Installing Grommet dependencies...
  3. If the install fails, make sure...
  4. A few harmless warnings
  5. Culminates with "Binary is fine; exiting."
  6. List of package installs

The hang occurs after the following 2 messages:
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.

NOTE: Even when I use grommet new --help as recommended by @alansouzati and set values, the hang persists.

Expected Behavior

The generator for the sample-app should complete without hang or error.

Actual Behavior

It seems that no matter what the approach, when using official documentation, the generation of the sample-app does not complete successfully.

Steps to Reproduce

Mentioned above.

Your Environment

  • Grommet version: 0.1.2
  • Browser Name and version: Never get to browser considerations
  • Operating System and version (desktop or mobile): Desktop, OS X El Capitan 10.11.6
@alansouzati
Copy link
Contributor

alansouzati commented Aug 10, 2016

Pending on an existing PR for Vorpal: dthree/vorpal#169.

In the meantime, I've released 0.1.3 that points to my fork to avoid this issue. Let's keep it open until this is resolved in Vorpal itself.

Thanks for the detailed information on the issue.

@alansouzati
Copy link
Contributor

It seems that the main branch repo is not active. i will use my fork instead.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants