Sami Vaarala
Sami Vaarala
The serialization is currently limited to a single function (or program). Serializing dependent functions would quickly become equivalent to generic serialization of arbitrary heaps because there may be loops, scoped...
That's true, there are a few bugs/issues which affect some corner cases of compatibility. But actually Duktape, and several other engines, are also no longer fully ES5.1 compatible because some...
@kphillisjr Renamed the issue because ES2015 support is a longer term target so it's not a feature request as such. There isn't a full set of Github issues addressing all...
Related discussion of some implementation details in #1344.
These are not implemented yet.
I can't promise a specific time, it all depends on how much free time I (or others) have to spend on development. In the meanwhile you can use transpiling, e.g....
I'm sure some workaround is possible in the serialization, either through the existing circular reference detection or simply limiting the size of the output and allowing a truncated value rather...
Sorry, I had missed this pull entirely. I can merge the pull but first you'd need to open a pull to the main duktape repo to add yourself to the...
Ah ok, that's not merged yet. So let's work through that first.
Ah, the text was not yet finished but just drafting a bit. As of Duktape 2.x config options are always handled via configure.py, never by defining them on the command...