Kevin Gibbons
Kevin Gibbons
Ecmarkup leaves a lot of stuff in the output document which is only really intended to be consumed by ecmarkup itself - for example, the `title` attribute of `emu-xref` tags...
PRs like https://github.com/tc39/ecma262/pull/1939 and https://github.com/tc39/ecma262/pull/1896 could (and should) be done automatically as part of the tooling. @mathiasbynens maintains a [collection](https://www.npmjs.com/search?q=keywords:unicode-data) of npm modules which could be used for this. Note...
I don't think anyone is using it, and it'll make linting more complicated.
Since https://github.com/tc39/ecma262 is the main consumer of this project, I think it would make sense to render it on every PR using the PR's branch of this project, so we...
See https://github.com/tc39/ecma262/pull/1800
(@michaelficarra) See for example this test: https://github.com/estools/escope/blob/f237eefd4bfadfcf397e451219c3079e9bc3bb81/test/es6-destructuring-assignments.coffee#L340-L346 Note that there are two references with name `c` and `isWrite()` true: that is, two write references to `c`. This despite the fact...
I'd like to try to port at least some subset of the client part of this project to other languages (particularly JS; cf #2). But that's hard without at least...
I ran a fuzzer for a while and found the following cases which are incorrectly rejected. Other than the first two they don't make sense as programs, although that's mostly...
Since [the `private` setting](https://docs.npmjs.com/cli/v7/configuring-npm/package-json#private) prevents `npm` from attempting to publish a package, there's no need for `publishConfig` to be configured for those packages.
I saw in the readme > Ability to generate code without any early errors. The fact that shift-fuzzer doesn't do this already is a bug, but not one I'm likely...