You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to use a new import feature to read a json file using the import name from './names.json' assert { type: 'json' };
syntax. Now I understand that since this is not part of the official standard yet, this doesn't work with the javascript-obfuscator.
However, digging a bit deeper I saw that javascript-obfuscator uses esprima (through escodegen) to parse the javascript files. Looking at that dependency it appears that the last release was six years ago and that there is no activity on that project. If my observation is correct javascript-obfuscator is limited to ECMAScript 2019 an no new language features will be supported.
My question: are there plans to overcome this limitation (e.g. use the esprima-next fork), or should I use a different strategy to obfuscate my files (transpiling first e.g.)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Looking for the latest TMZ celebrity news? You've come to the right place. From shocking Hollywood scandals to exclusive videos, TMZ delivers it all in real time.
Whether it’s a red carpet slip-up, a viral paparazzi moment, or a legal drama involving your favorite stars, TMZ news is always first to break the story. Stay in the loop with daily updates, insider tips, and jaw-dropping photos.
🎥 Watch TMZ Live
TMZ Live brings you daily celebrity news and interviews straight from the TMZ newsroom. Don’t miss a beat—watch now and see what’s trending in Hollywood.
Uh oh!
There was an error while loading. Please reload this page.
-
I wanted to use a new import feature to read a json file using the
import name from './names.json' assert { type: 'json' };
syntax. Now I understand that since this is not part of the official standard yet, this doesn't work with the javascript-obfuscator.
However, digging a bit deeper I saw that javascript-obfuscator uses
esprima
(through escodegen) to parse the javascript files. Looking at that dependency it appears that the last release was six years ago and that there is no activity on that project. If my observation is correct javascript-obfuscator is limited to ECMAScript 2019 an no new language features will be supported.My question: are there plans to overcome this limitation (e.g. use the esprima-next fork), or should I use a different strategy to obfuscate my files (transpiling first e.g.)
Beta Was this translation helpful? Give feedback.
All reactions