Prepack helps make JavaScript code more efficient

Re:Prepack helps make JavaScript code more efficient by tyingq on Wednesday May 03, 2017 @01:43PM (#14258174)

How "safe" is it? I'm thinking, for example, of Google's closure compiler and the advanced optimizations, which can break some things.

Or roughly, if it compiles without errors, is it safe to assume it won't introduce new bugs?

[ Parent | on HN ]

Re:Prepack helps make JavaScript code more efficient by NTillmann on Wednesday May 03, 2017 @01:51PM (#14258273)

It's not yet ready for production, so there are some bugs and cases where we should reject a program but don't do that yet.

Having said that, it's quite safe, but won't be undetectable. Code using eval could detect injected identifiers, we don't currently aim at preserving function names, and the method bodies you get with toString() are altered. That should be roughly it.

[ Parent | on HN ]

Re:Prepack helps make JavaScript code more efficient by Hydraulix989 on Wednesday May 03, 2017 @01:55PM (#14258311)

The real litmus test: Does FB use it in production yet?

[ Parent | on HN ]

Re:Prepack helps make JavaScript code more efficient by newman314 on Wednesday May 03, 2017 @03:36PM (#14259260)

Has this been tried on popular JS packages such as jquery?

[ Parent | on HN ]