Skip to content
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

Jump to bottom

debug is not defined in $env.log() #19

Closed
fiann opened this issue Aug 12, 2010 · 2 comments
Closed

debug is not defined in $env.log() #19

fiann opened this issue Aug 12, 2010 · 2 comments

Comments

@fiann
Copy link

fiann commented Aug 12, 2010

I found this when loading a script by inserting a DOM script node, and the script URL gives a 404.

Here's the relevant part of the stack trace:

Exception: TypeError: debug is not a function
/opt/local/lib/ruby/gems/1.8/gems/envjs-0.3.7/lib/envjs/env.js:148 ("could not load script http://localhost/core/javascripts/script-loader-badfile.js: 404 Not Found","...
/opt/local/lib/ruby/gems/1.8/gems/envjs-0.3.7/lib/envjs/env.js:693 ("could not load script http://localhost/core/javascripts/script-loader-badfile.js: 404 Not Found")
/opt/local/lib/ruby/gems/1.8/gems/envjs-0.3.7/lib/envjs/env.js:816 ([object Object],null)

The reason is that $env.log() calls debug() not print()
@fiann
Copy link
Author

fiann commented Aug 12, 2010

There's a fix here. http://github.com/fiann/env-js/commit/72fc80bf1e5b09b2e2dbd3003b0a49998922bbb1

Changing this outputs a lot of additional warnings when running the build, which may or may not matter.

@smparkes
Copy link
Owner

Thanks.

The build's always printed a lot of warnings, I think.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smparkes @fiann