-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm install missing /dist #145
Comments
This might be because of the gitignore. @paulcpederson want to try deleting it as part of branch build push tag release process? |
The release includes a #146 makes that more explicit in the |
Yeah true, because of the way we're handling dist files they won't be in master, so you need to install the version explicitly like so:
You know @paulcpederson now that npm supports private modules we could actually put this up on npm and not have to install privately through github. |
@ngoldman yeah I looked into that. That would force everybody that wants to use it to also have an npm private account. So nik, me, you, pat, cassidy, long, justin, etc... Hundreds of people all need a private account. I think our hacky "GitHub access as module security" scheme will work for now. Hopefully when npm launches their organization support we can register calcite-web as an organization repo and that could be a way forward. As long as we explicitly state that you must install @ a specific tag, I think it makes sense to force users to use a release. In your |
I see their evil strategy now. No org accounts. |
Not too familiar npm's package.json handling, so I might be missing something, but the following steps did not include /dist:
Specifying the version as a workaround.
The text was updated successfully, but these errors were encountered: