npm add -D js_storage
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/js_storage - Not found
npm ERR! 404
npm ERR! 404 'js_storage@latest' is not in the npm registry.
Hey there JB — I wrote these articles a long time back on a Ghost blog server I maintained myself and then ported them over to Medium but missed a few things in translation. I’ll be addressing these issues in the coming weeks, and I’ll post a response to you when I fix that. Thanks for the feedback and I hope you can be patient with me :)
This looks like a really good framework — documentation tends to be something that is overlooked even more than testing. Our teams are using TDD and finding a great deal of success with it, but you still have to account for the fact that at some point you are handing your code over to someone else to maintain. Or maybe you are writing something you…
Looks a lot like what we are doing with enzyme and jest but I do like the way it organizes the test cases in ways that are analogous to the way that testers write their test cases. The easier it is for someone who isn’t deeply technical to write the tests, the better. I’m going to have to check out RITEway and Tape.
Great article. I came to a new company where someone had set up the Webpack/express stack, but it wasn’t done correctly to expose the source maps so you could correctly debug from the browser and tools like WebStorm. I worked some of that out and I’ll hopefully have an article on it soon, but I like the way you laid this out. I hope that one day…
Great topic with a lot of philosophical value. I’m generally of the opinion that once you find something isn’t as you expected (i.e., you can’t open a file, can’t reach an API endpoint, etc), you pretty much need to bail, but you may need to handle it gracefully to avoid a bad user experience. Normal humans don’t care about the details (i.e., what…