-
-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TS 3.8.x ES private fields are not taken in account #1054
Comments
I suspect you're either not using the 3.8 version of TypeScript or something is awry with your configuration. I'm not aware of a need for any changes required to ts-loader to facilitate this. |
tested on: So I guess the issue is related to ts-loader. Tried also |
// sorry for double post I went to: node_modules/ts-loader/dist/index.js on:
So it looks like the compiler is loaded correctly but error on output |
I found someone with the same issue: I also find out it comes from ACorn package. Where code This function doesn't take in account 35. So it seems to be Webpack issue |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as stale. Please reopen if you'd like to work on this further. |
On Jan 10 was released typescript 3.8 beta. But we are not able to compile private fields from ecmascript.
Expected Behaviour
To compile code without issues
Actual Behaviour
Steps to Reproduce the Problem
Create project with TS 3.8 beta, use tslib from git and use ts-loader with webpack.
Create a class with EcmaScript private field.
Location of a Minimal Repository that Demonstrates the Issue.
Trivial to replicate, it is not needed.
packages:
tsconfig:
The text was updated successfully, but these errors were encountered: