-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Underscore fetched with bower stopped working #2923
Comments
No that was not expected and not intended. Thanks for reporting, @kopernic-pl! I don't know much about Bower, to be honest; the bower.json file was already there when I took over maintenance and I never touched it. I'll look into it, but if you have any tips on how to solve the issue, please let me know. |
@kopernic-pl I took a look at the bower.json, and it seems I actually updated it to use Seems like the only way to address this is to commit the duplicate |
No opinion on this one on my side - I'm just upkeeping some legacy project ;) It's ok for me to use undescore-umd.js but I'm afraid that it will still break something somewhere, in some other projects. Btw, symbolic links are no-go, so eventual copy seems to be only solution. Maybe name the file in the repo 'undescore.js' and automate renaming/creating copy to 'underscore-umd.js' when NPM package is created? |
Btw, the 'main' in bower.json just states which files from repository should be pulled to your lockal packages when doing bower init., as per bower spec It does not do nothing with files renaming. Bower is prehistoric nowadays 👴 |
I just ended up here because my build of a legacy project failed when uglifyjs reported it could not find I'll point my uglifyjs config to underscore-umd.js for now (at least that's my take away from this thread here. I didn't know if I would need esm, node or umd 😄 🙈 ) |
@kopernic-pl I won't change the official name of the UMD build back to @7ochem Thanks for chiming in. Your legacy project almost certainly needs the UMD build. I guess I should add some clarification about that to the documentation. If you have any suggestions for questions that you'd like to see answered with regard to that, please feel free to let me know. |
I've just pointed my code to umd package from 1.13.0 and it works very well (with require.js as a loader). So for me it is solved, for others @jgonggrijp copy shall be more than OK for next few years :) |
@kopernic-pl @7ochem 1.13.1 is up. |
Thank you for the fast response and the ultra fast fix! 🙏🏻 |
Welcome! |
There is a difference in how 1.13.0 fetches using NPM and bower.
npm package contains backward-compatibility underscore.js file (underscore-umd copy, as confirmed with diff)
bower, fetching directly from github, does not contain underscore.js file, which genreally breaks a lot.
Is it expected behavior?
The text was updated successfully, but these errors were encountered: