最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

typescript - How can I use JavaScript private fields in VS Code? - Stack Overflow

matteradmin7PV0评论

I'm using the proposed private field syntax in my JavaScript but VS Code says this is a syntax error:

The specific error is: Invalid character. ts(1127)

How can I make VS Code understand private fields?

I'm using the proposed private field syntax in my JavaScript but VS Code says this is a syntax error:

The specific error is: Invalid character. ts(1127)

How can I make VS Code understand private fields?

Share Improve this question asked Jan 8, 2020 at 7:05 Matt BiernerMatt Bierner 66.1k24 gold badges198 silver badges230 bronze badges
Add a ment  | 

1 Answer 1

Reset to default 7

Cause

VS Code uses the TypeScript project to power both its JavaScript and TypeScript IntelliSense. The TypeScript project only added support for private fields in TypeScript 3.8. However the current release of VS Code (1.41) only includes the latest stable TypeScript 3.7 release.

If you see syntax errors for private fields, you are likely using a version of TypeScript in VS Code that does not yet understand private fields.

Workaround

VS Code 1.43 (to be released early March 2020) will include TypeScript 3.8. Until then, you can upgrade your workspace to use a newer typescript version by either:

  • Installing this extension

  • Following these instructions

Keep in mind that other VS Code extensions—such as linters—may also need to be updated with support for private fields

Post a comment

comment list (0)

  1. No comments so far