bergsans / archaize-js Goto Github PK

Archaize JS currently doesn't handle !==

While this works:

function someFunc(...props) {
// ...
}

This doesn't work:

function someFunc(param, ...props) {
  console.log(param);
}
someFunc("some param!");

There are known bugs that emerges when the user uses to much nesting. This is related to issue #5

this works...

const someString = 'hello, world!';

this doesn't work:

const someString = strings.reduce((a, b) => ...

Given time, the transpiler would need a total re-write. The main problem, I think, is that the transpiler is a 'patch work'. For every new feature, it would have to add and patch other features (and so on). The result in a labyrinth-like code-base. To put it bluntly: the code quality could be improved quite a lot.

Considering the deadline, this is however something that would have to be done later.

-t flag doesn't work. --transpile works though (unclear why).

These method should make us of a optional second and third parameter according to the ECMAScript Specification. Because they don't, it's impossible to use the find and findIndex correctly whenever a second and third parameter is passed to them.

This works:
[...something, var]
But not:
[...arr1, ...arr2]

This doesn't work:

const someArrowFunction = () => {}