Javascript Stacktrace Ignite
•Télécharger en tant que KEY, PDF•
0 j'aime•1,183 vues
Bite-size talk on the Javascript Stacktrace project
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (16)
En vedette
Similaire à Javascript Stacktrace Ignite
Similaire à Javascript Stacktrace Ignite (20)
Javascript Stacktrace Ignite
- 1. The JavaScript Stacktrace Project Making cross-browser compatibility suck a little less © 2010 Eric Wendelin
- 2. Let me say this upfront... You care about this project* * Probably
- 3. D’oh!
- 4. What would you do?
- 5. IE Developer Tools Yay... won’t this be fun?
- 6. What if you could get...
- 7. Javascript Stacktrace Micro-library for getting function stack traces in all* web browsers * NOTE: Must actually support Javascript
- 8. In a nutshell... printStackTrace() return [ ‘calledFromFoo(my.js:32)’, ‘foo(my.js:23)’, ‘callsFoo(my.js:14)’, ‘{anonymous}(other.js:1)’, ... ]
- 9. Licensed to the public domain ~1.8k minified and gzipped
- 10. Works in
- 11. How it works function foo() { //calling function! arguments.callee.caller //passed parameters! arguments.callee.caller.arguments }
- 12. Bonus: Error objects try { (0)(); // produce an error } catch (error) { error.stack; // Firefox, Chrome error.stacktrace || error.message; // Opera }
- 13. Step 1: <script type=”text/javascript” src=”stacktrace.js”></script> Step 2: var trace = printStackTrace(); Step 3: showError(trace.join(‘n’));
- 15. • Now at 5 contributors • 130+ watchers on GitHub
- 16. Coming soon... • IE9 support • Function instrumenting to always print a stacktrace when called (done!) • Real-time traces (maybe! - not as easy as you think ;)
- 17. Secrets to open-source success
- 18. Good idea > good skill
- 19. Unit tests help others contribute
- 20. Just release it
- 21. su.pr/AH9ShK [ http://github.com/emwendelin/javascript-stacktrace ] Blog: eriwen.com Twitter: @eriwen Email: emwendelin@gmail.com © 2010 Eric Wendelin
Notes de l'éditeur
- Do you write any JavaScript? Does your web app have to behave in Internet Explorer?
- This is a Javascript developer&#x2019;s nightmare. Don&#x2019;t you love IE?
- Open up Firebug, try to reproduce the bug... and come to the realization that you&#x2019;ll have to debug it in IE.
- Unfortunately, the developer tools available for IE aren&#x2019;t always that helpful. At this point you&#x2019;re reduced to console.log statements or even... *gasp* alerts.
- What if you had a way of knowing what was called leading up to the error automatically?
- An array of strings containing function names, files, line numbers and arguments
- Obviously this project is open-source or I wouldn&#x2019;t be speaking to you tonight. So you have no excuses not to use it!
- Javascript Stacktrace works in LOTS of browsers. I have tested it as working in IE 5.5 up, and all the other browsers you see here... probably many of which you may have never heard of
- The secret sauce here is that every function has a reference to it&#x2019;s calling function, that every function maintains a reference to passed parameters
- Good browsers have Error objects that have a function stack complete with files and line numbers!
- 3 simple steps to get this working: Include stacktrace.js, call printStackTrace() and do whatever you want with it. In the previous example I called it within window.onerror
- You can&#x2019;t get everything in all circumstances. Only gives you where the problem is, not what. Not interactive without a console.
- However, it is one more tool in your toolbox, and it turns out a bunch of people think it&#x2019;s useful enough.
- I know a lot of you attended my talk in February, so for you I have a sneak peek of things to come
- I learned a lot about how to manage open-source projects themselves, and I wanted to share a few secrets that I think apply to all projects
- It turns out it usually doesn&#x2019;t matter HOW you do it as long as you fulfill a need.
- Using QUnit for unit testing and Browsershots.org to test lots of browsers visually encouraged everyone to make code tweaks without fear!
- I, myself, am guilty of not releasing projects because I was afraid of looking stupid and having my code laughed at. It is *always* worth it to publicize it, anyway. You are guaranteed to learn a lot
- Now go check out the project! Hit the shortlink here or just Google &#x201C;Javascript Stacktrace&#x201D; and it&#x2019;s the first result!