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
How do I enable debug in jade loader #40
Comments
Can you provide more details? What message do you see? What would you expect? |
I am using wpt dev-server.sh What I see: What I would like to see: On a related topic: it is also difficult to trace javascript errors, it would save me a lot of time if this could be improved as well Thanks, Kavaro Op 14-nov.-2012, om 23:14 heeft Tobias Koppers het volgende geschreven:
|
I tried it with
This should be so. (I fixed a bug in the jade-loader and it should be so for jade also) The evaling with In Chrome dev tools it looks like this:
webpack-module:///./~/jade-loader!./app/test.jade:28 is a clickable link which opens the "Source" tab with the compiled "test.jade" source only. On the left side is a hierachie with all loaded webpack modules. |
How do I install your fix ? Have changed my package.json devDependencies to the following:
followed by 'npm install' Introduced the error: a(a=a, The html body is now empty, so, for sure there is a jade error, however dev-server.sh does not fail and there are no error messages. On the issue about javascript source files: However in firebug I get the following message: (the error is ReferenceError: doesnotexist, this error occurs in ../../app.js line 15, however I don't see the source line number), I am using firefox 16.0.2
Op 15-nov.-2012, om 09:26 heeft Tobias Koppers het volgende geschreven:
|
ok something seem to be buggy... maybe this applies here: http://code.google.com/p/fbug/issues/detail?id=2198 You can disable the "eval" stuff with
and add these lines to options.debug = false;
options.includeFilenames = true; // this include filenames in comments or use chrome for debugging
|
Seem to be a firebug bug: http://groups.google.com/group/firebug/browse_thread/thread/8632fe7e6a7e1c4f Your package.json is ok, you can even leave it Unfortually |
Thx for the super fast responses. There indeed seems to be a firebug bug :-) Tried the new jade-loader using a fresh install with the latest wpt: Any ideas why an error in body.jade does not cause an error message and stop the build. Op 15-nov.-2012, om 13:50 heeft Tobias Koppers het volgende geschreven:
|
ah ok... Now I see the problem... First you should not edit any file in // _template/index.jade
- try {
!= require("../app/body.jade")(locals)
- } catch(e) {} I'll replace this with file existance detection, so it fail if a error in the jade occurs. I thought you did something like // app/app.js
var template = require("./test.jade");
document.write(template()); To update to a new wpt version run:
|
Hi @sokra
I am unable to see error messages from jade loader.
I assume I need to set debug flag for the loader, how do I do this.
I am working with wpt and dev-server
thx,
Kavaro
The text was updated successfully, but these errors were encountered: