Default value is not set for uint32 fields when using decorators

[azerum]

protobuf.js version: 7.10.1

Please describe the expected and actual behavior

If I create Vector message instance without setting fields, they will have default value for numbers - 0:

@Type.d()
export class Vector extends Message<Vector> {
    @Field.d(1, 'double')
    x: number;

    @Field.d(2, 'double')
    y: number;
}

const v = new Vector();
console.log(v.x, v.y); //0, 0

However, if I change types to uint32, fields are undefined:

@Type.d()
export class Vector extends Message<Vector> {
    @Field.d(1, 'uint32')
    x: number;

    @Field.d(2, 'uint32')
    y: number;
}

const v = new Vector();
console.log(v.x, v.y); //undefined, undefined

Is this intended?

P.S.

As I understand, in proto3 all fields are 'optional' in sense
that sender can omit them. However, receiver will always have a message that has
all fields set: if field was not set by the sender, it will get a default value fitting it's type (null for message types, 0 for number, false for boolean etc). Is this correct?

Also, when using decorators, does protobufjs work in proto3 or proto2 mode?