8000 Attempting to load minified Lo-Dash results in Uncaught ReferenceError · Issue #19 · lodash/lodash · GitHub
[go: up one dir, main page]
Skip to content

Attempting to load minified Lo-Dash results in Uncaught ReferenceError #19

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.

Sign up for GitHub

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

Jump to bottom
Closed
Guiswa opened this issue May 29, 2012 · 2 comments
Closed

Attempting to load minified Lo-Dash results in Uncaught ReferenceError #19

Guiswa opened this issue May 29, 2012 · 2 comments
Labels
bug

Comments

@Guiswa
Copy link
Guiswa commented May 29, 2012

See this fiddle:

http://jsfiddle.net/XCsuX/

Attempting to load the minified Lo-Dash (https://raw.github.com/bestiejs/lodash/master/lodash.min.js) results in the following error in the console:

"Uncaught ReferenceError: obj is not defined"

Changing the fiddle to load the unminified version (https://raw.github.com/bestiejs/lodash/master/lodash.js) works as expected without error.

This is reproducible every time for me on:

Windows 7 x64
Google Chrome 21.0.1145.0
Mozilla Firefox 12.0
@jdalton
Copy link
Member
jdalton commented May 29, 2012

Thanks, that was an issue introduced while closing issue #16. It should be resolved now. Edge is living on the edge.

jdalton added a commit that referenced this issue Aug 29, 2013
@jdalton
Cleanup build.js and fix regression in minified build. [closes #19]
c8e12fb 
Former-commit-id: 5782396
jdalton added a commit that referenced this issue Sep 25, 2014
@jdalton
Cleanup build.js and fix regression in minified build. [closes #19]
a5712fc 
Former-commit-id: 3b455cb277fa8c3fc70efca7b54c6746cde2ea6b
@lock
Copy link
lock bot commented Jan 21, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jdalton @Guiswa
0