This repository has been archived by the owner on Feb 15, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 329
react-component generator not working #21
Labels
Comments
Looks like Investigating now. |
It looks like npm is reading the |
thanks so much! Amazing response time hahaha :-) |
This is fixed in the npm package for 0.4.1. The source of the problem isn't fixed, will do that later. |
This was referenced Dec 13, 2015
👍🏼🏼👍🏼 all is well. thanks! |
NP, thanks for the bug report 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Great work here so far - extremely useful for bringing a set of ember-cli-like conventions which is sorely needed in the React community IMO.
I am attempting to use
nwb
to create a higher-order react component. The problem is that when I generate a component using:nwb new react-component my-component
I am asked about UMD and give it a global.
It creates the directory and installs dependencies.
the resulting directory looks like this:
However, when i create an
app
with nwb, the structure is correct:and with web-modules:
any idea what could be causing this?
Thanks!
The text was updated successfully, but these errors were encountered: