ModuleImport

Kevin Smith zenparsing at gmail.com
Sat Jun 28 16:01:31 PDT 2014


>
>
> Usually, I obtain the same benefit running the tests (and more, test that
> were the product of TDD workflow). In this way, I'm sure not only of no
> removal of something I needed, but also the underlying behavior of imported
> modules are still the same. Relaying on static imports only warns me about
> the presence or not of some functions, but the app could be
>

Of course, there's no substitute for unit tests with good coverage.  But
the question is, what kind of help does that language provide for static
analysis?  Currently, JS provides almost none.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140628/a7a9bba5/attachment.html>


More information about the es-discuss mailing list