3 ms·
After several hours I figured it out. My biggest problem was that I had the same sentiment as your comment in "because you're maybe missing a line of code." I k
by zappo2938 10y ago
After several hours I figured it out. My biggest problem was that I had the same sentiment as your comment in "because you're maybe missing a line of code." I kept blaming myself when it was a bug in a popular module one of only a handful I'm using.
- seanwilson 10y agoJust remember you're in good company! I find a lot of coding involves you trying to do something, getting an error, you look up the error, you try the solution you find, you get a new error and so on. Many people will give up after a few hurdles. I tried to port an Angular 1 to Angular 2 recently and fixing issues to do with just getting the JavaScript modules/files to load drove me up the wall. I was close to giving up but after working through several layers of issues it eventually worked. Sounds like it was an similar experience to you...there's so many permutations of JavaScript stacks you can use that isolating the issue is like finding a needle in a haystack sometimes. What I mean is that sometimes all you can do it be persistent and realise that switching to a new framework could just introduce lots of new issues.