-
Notifications
You must be signed in to change notification settings - Fork 25
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
Package hoodie-client for Bower #142
Comments
bower is deprecated as far as I know. And it’s problematic because we need to commit built files to the repository. What’s your use case? Install via npm should usually work |
I believe Bower is still supported, though I agree that npm is being used more widely these days for frontend dependencies. The use case is that I'm building a workshop based on the Polymer Shop app. This app uses Bower to install dependencies. For now, I'm simply loading the Hoodie client from the Hoodie server. However, it would be nice to be able to treat the frontend app as its own independent app with its own dependencies. |
I think bower can install directly via a URL, you can use this one: https://unpkg.com/@hoodie/[email protected]/dist/hoodie.js It is the built version of |
This does not seem to work:
Nor any variation such as:
However, installing directly from GitHub seems to work:
This should be good enough as a work around. Thanks! |
note that we don’t have the built version of Telling from their own docs at https://bower.io/docs/api/#install, bower install https://unpkg.com/@hoodie/[email protected]/dist/hoodie.js should just work ¯\_(ツ)_/¯ |
I saw some talk of a potential bug with Bower that could explain why the install from unpkg didn't work, but I didn't spend a ton of time exploring that. Oh well. This should work for now. Hopefully Polymer moves away from using Bower in their application templates and demos. |
For reference: Polymer/polymer#326 (comment) |
I would like to be able to install
hoodie-client
via Bower. See the instructions for creating bower packages for reference. In my understanding, this would include:bower.json
file.bower.json
.Step 4 could be a blocker, as there appears to be third party dependencies that are not already packaged up as Bower components.
The text was updated successfully, but these errors were encountered: