in es3, "use strict" should not be parsed as directive

[aladdin-add]

no nodes should be parsed as Directive nodes in ES3 mode. it was found in eslint/js#547 (comment)

related: 353e24f

[marijnh]

I think this was fixed in 353e24f . Can you confirm?

[aladdin-add]

to clarify, I was using the newly released acorn v8.7.1. it was partly fixed, an example:

"use strict";
var foo = 00;

• in acorn<v8.7.1, parsing it will throw an error "invalid number".
• in acorn v8.7.1, it can be parsed successfully, but "use strict" is still parsed as a directive. you can see the parsed result here: https://github.com/eslint/espree/blob/7178c4f877afeb24af6472e9f15e039c8a7988e5/tests/fixtures/ecma-version/3/strict/use-strict.result.js#L53

[marijnh]

I see what you mean now. Attached patch should help.

[ljharb]

@marijnh is there any clean way via a plugin (that i can add via eslint config) to revert these changes? in other words, i want to enforce ES3 syntax but respecting strict mode semantics, so that I can upgrade eslint beyond v8.8.0.