NPM package is broken when installing from a github url #20
Comments
The lib folder is missing your your hierarchy.. That's weird! I'll take a look. |
Maybe the problem occurs because I install the package from my fork at github:
And I can't try to install it from npm because it's version doesn't include my pull request (yet, I think) because of react version conflict. |
@web2style do yo run the buildscript after you install ? |
No. There's nothing about it in the README. |
Because you're getting the files from github, you actually don't have the compiled files. Therefore, you have to compile the files yourself with The compiled files are only pushed on NPM when a new version is published. |
When installing from github, there's no |
Hmm.. Not sure how to fix this thing. Maybe someone has an idea? I'll reopen, maybe someone can help here. |
How about registering a browserify transform ?! So that browserify compiles
|
Any reason why you don't want to include the sources on NPM @tleunen ? |
The end user cannot do anything with the source since it needs a compilation step. So I was thinking to remove it from npm, but if it's the only solution to get the src folder when installing from github, I guess I'd remove it from the ignore file |
As long as the |
Installed the package via npm. When trying to import it:
I get the following errors:
There's no
lib
folder in the package directory:The text was updated successfully, but these errors were encountered: