截至2021年的最新浏览器(不是IE，请参阅MDN浏览器图表)实现了公共类字段，这似乎是你正在寻找的:

MyClass { 静态foo = 3; ｝ console.log (MyClass.foo);

然而，显然不可能使这是一个const:在ES6类中声明静态常量?

静态getter看起来非常接近:

MyClass { 静态获取CONST() { 返回3; ｝ ｝ MyClass。Const = 4;//财产不受影响 console.log (MyClass.CONST);

由于您的问题主要是风格上的(不想用一堆声明填充构造函数)，因此也可以从风格上解决。

The way I view it, many class based languages have the constructor be a function named after the class name itself. Stylistically we could use that that to make an ES6 class that stylistically still makes sense but does not group the typical actions taking place in the constructor with all the property declarations we're doing. We simply use the actual JS constructor as the "declaration area", then make a class named function that we otherwise treat as the "other constructor stuff" area, calling it at the end of the true constructor.

"use strict";

class MyClass
{
    // only declare your properties and then call this.ClassName(); from here
    constructor(){
        this.prop1 = 'blah 1';
        this.prop2 = 'blah 2';
        this.prop3 = 'blah 3';
        this.MyClass();
    }

    // all sorts of other "constructor" stuff, no longer jumbled with declarations
    MyClass() {
        doWhatever();
    }
}

在构造新实例时，两者都将被调用。

有点像有两个构造函数，你可以把声明和其他你想要执行的构造函数动作分开，并且在风格上让它不太难以理解这是在发生什么。

我发现当处理大量声明和/或大量需要在实例化时发生的操作并希望保持这两种思想彼此不同时，使用这种风格很好。

NOTE: I very purposefully do not use the typical idiomatic ideas of "initializing" (like an init() or initialize() method) because those are often used differently. There is a sort of presumed difference between the idea of constructing and initializing. Working with constructors people know that they're called automatically as part of instantiation. Seeing an init method many people are going to assume without a second glance that they need to be doing something along the form of var mc = MyClass(); mc.init();, because that's how you typically initialize. I'm not trying to add an initialization process for the user of the class, I'm trying to add to the construction process of the class itself.

While some people may do a double-take for a moment, that's actually the bit of the point: it communicates to them that the intent is part of construction, even if that makes them do a bit of a double take and go "that's not how ES6 constructors work" and take a second looking at the actual constructor to go "oh, they call it at the bottom, I see", that's far better than NOT communicating that intent (or incorrectly communicating it) and probably getting a lot of people using it wrong, trying to initialize it from the outside and junk. That's very much intentional to the pattern I suggest.

对于那些不想遵循这种模式的人来说，完全相反的方法也可以奏效。在开始时将声明传递给另一个函数。也许可以命名为“properties”或“publicProperties”之类的。然后把剩下的东西放在普通构造函数中。

"use strict";

class MyClass
{
    properties() {
        this.prop1 = 'blah 1';
        this.prop2 = 'blah 2';
        this.prop3 = 'blah 3';
    }

    constructor() {
        this.properties();
        doWhatever();
    }
}

请注意，第二种方法可能看起来更干净，但它也有一个固有的问题，即当使用该方法的类扩展另一个类时，属性会被覆盖。为了避免这种情况，您必须为属性提供更唯一的名称。我的第一个方法没有这个问题，因为它的伪构造函数的一半是以类唯一命名的。

你可以在构造函数中声明变量。

class Foo {
    constructor() {
        var name = "foo"
        this.method = function() {
            return name
        }
    }
}

var foo = new Foo()

foo.method()

ES7类成员语法:

ES7有一个“废弃”构造函数的解决方案。这里有一个例子:

车{ 轮子= 4; 重量= 100; ｝ const car = new car (); console.log(车。轮子,car.weight);

上面的例子在ES6中看起来如下所示:

车{ 构造函数(){ 这一点。轮子= 4; 这一点。重量= 100; ｝ ｝ const car = new car (); console.log(车。轮子,car.weight);

使用此语法时请注意，此语法可能不是所有浏览器都支持，可能必须转译为早期版本的JS。

好处:一个对象工厂:

函数generateCar(车轮，重量){ 车{ 构造函数(){} 轮子=轮子; 重量=重量; ｝ 返回新车(); ｝ const car1 = generateCar(4,50); const car2 = generateCar(6,100); console.log (car1。轮子,car1.weight); console.log (car2。轮子,car2.weight);

正如Benjamin在他的回答中所说，TC39明确决定至少在ES2015中不包含这个功能。然而，共识似乎是他们将在ES2016中添加它。

语法还没有决定，但是ES2016已经有了一个初步的提议，允许你在一个类上声明静态属性。

多亏了巴别塔的魔力，你今天可以使用它。根据这些说明启用类属性转换，就可以开始了。下面是一个语法示例:

class foo {
  static myProp = 'bar'
  someFunction() {
    console.log(this.myProp)
  }
}

这个建议还处于非常早期的状态，所以准备好随着时间的推移调整您的语法。

[长线程，不确定它是否已经列为一个选项…]。 仅用于常量的一个简单替代方法是在类外部定义const。 除非附带getter，否则只能从模块本身访问。 这样原型就不会被乱扔，你就能得到const。

// will be accessible only from the module itself
const MY_CONST = 'string'; 
class MyClass {

    // optional, if external access is desired
    static get MY_CONST(){return MY_CONST;}

    // access example
    static someMethod(){
        console.log(MY_CONST);
    }
}