-
Notifications
You must be signed in to change notification settings - Fork 217
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
Unable to install with bower #63
Comments
How are you requiring/importing deepmerge? |
Are you using bower? |
I'm not sure exactly what issue you were having, but I published 1.4.3 to inline is-mergeable-object for folks using bower who are trying to bundle the CommonJS entry point. Let us know what your environment is @smarbiv, and whether or not 1.4.3 works for you. |
Thanks for your quick response. |
1.4.3 no longer relies on you downloading the is-mergeable-object module - the code is inlined in every version of the file that is distributed on the npm registry. Does bower not use the npm registry? Does it require that the built files be on Github? I'm not familiar with bower's workings at all. |
hmm, at the very least, it looks like I forgot to update the |
Hi, |
I published 1.4.4 with an updated bower.json, let me know if that works for you. What bundler are you using? I didn't think to ask this when Bower was discussed before, but I'm curious what bundlers look at bower.json at all. |
I'll assume everything is fine and dandy now :-) |
Hi, |
Could you depend on the unpkg link? https://unpkg.com/deepmerge/dist/umd.js |
Yes, that works for me! :) |
I wonder if there's something I could put in the bower.json that would save other bower users from running into this |
Your fix in 1.4.4 could work if the file was exists, so adding the dist folder with the umd.js file to git maybe could be a solution.. |
Is bower support worth adding build artifacts to the repository? |
I'm leaning towards no :-x |
Merging #69 will officially drop Bower support via the Github repo. |
Hi,
I have an issue with the latest release (1.4.1), it looks like the module uses 'is-mergeable-object' which is missing...
The text was updated successfully, but these errors were encountered: