nolanlawson / optimize-js

Optimize a JS file for faster parsing (UNMAINTAINED)

https://nolanlawson.github.io/optimize-js

nolanlawson/optimize-js Issues

Vulnerability GHSA-7FHM-MQM4-2WP7
Updated 3 years ago
Unrecognised character '#' on line 1
Updated 6 years ago
Can you update tests in README to current browser versions?
Updated 7 years ago1
Add an option to read sourcemap
Updated 7 years ago9
Reaches parse error with async functions
Updated 7 years ago
Memory leak
Updated 7 years ago3
walk.js aborts with error if input contains ES6 code
Updated 8 years ago8
Is the readme correct?
Updated 8 years ago1
Not as optimized for Browserify as it could be.
Closed 8 years ago3
Encoding problem
Updated 8 years ago2
Heuristic improvement: don't paren-wrap lazy-require()d modules
Updated 8 years ago
Benchmark unfairly excludes compilation time.
Closed 8 years ago4
Do minifiers undo this?
Closed 8 years ago1
Is there a browser side version?
Closed 8 years ago2
Made a Ruby gem
Updated 8 years ago
I made a Web UI for optimize-js
Updated 8 years ago
Benchmark doesn't appear to work.
Updated 8 years ago
Bad Readme example?
Closed 8 years ago2
Not as optimized for Webpack as it could be
Closed 8 years ago13
make a babel-plugin ?
Updated 8 years ago5
uglify > optimize source map
Updated 8 years ago1
Use benchmark.js or similar, report standard deviation
Updated 8 years ago
Have you tested angularjs v1 and v2?
Updated 8 years ago1
Option to set input source map
Closed 8 years ago1
similar repositories using js engine tricks ?
Closed 8 years ago1
Comparison with Google's Closure Compiler?
Closed 8 years ago2
Benchmark script's improvement calculation is off a bit
Closed 8 years ago4
Clarify what is being faster
Closed 8 years ago16
Your math is wrong
Closed 8 years ago1
Smarter function-passed-to-function heuristics?
Updated 8 years ago5
Feature Request or missing Documentation?
Closed 8 years ago2