4 ms·
You can see what your functions do by opening the file called util.js in the same directory. And, yes you can run this in the browser by either polyfilling "req
by robjan 6y ago
You can see what your functions do by opening the file called util.js in the same directory. And, yes you can run this in the browser by either polyfilling "require" or transpiling it
- TekMol 6y agoBy that logic, everything runs in a browser. The principle of computational equivalence tells us that one turing complete language can do what any other can. So yes, everything can be polyfilled or transpiled. But that does not really meet my understanding of "Runs in the browser".
- sillysaurusx 6y agoIf you run browserify on an index.js file, it will usually spit out a single .js file that will run in the browser.
- tlrobinson 6y agoWhen I open https://tomcoin.herokuapp.com/ https://tomcoin.herokuapp.com/ in a browser I see it running. That meets my definition of "runs in the browser". Would you have been happier if I wrote "written in a dialect of JavaScript which is transpiled to ES5 using Webpack and Babel so it can run in the browser"?
- ric2b 6y agoComputational equivalence doesn't include things like networking and resource access if you run in a sandboxed environment.