Skip to content

Releases: timostamm/protobuf-ts

v2.0.0-alpha.18

13 May 21:25
Compare
Choose a tag to compare
v2.0.0-alpha.18 Pre-release
Pre-release
v2.0.0-alpha.18

Accident reversal

06 Apr 18:04
Compare
Choose a tag to compare

v2.0.0-alpha.18 was accidentally published in the "latest" channel.

This release is identical with v1.0.12, it just fixes the "latest" NPM release.

Do not output source mappings and declaration mappings

16 Dec 20:29
Compare
Choose a tag to compare

This patch removes source mappings and declaration mappings from
the npm packages. See #40.

Thanks to @johnsoncodehk and @tlstyer for the reports.

Bugfix for windows import path

27 Nov 22:21
Compare
Choose a tag to compare

This patch fixes generated import path on windows platform.
Thanks to @SyedAsimAliSE for bringing this issue up.

Bugfix for jstype = JS_STRING field option for speed optimized code

19 Nov 10:15
Compare
Choose a tag to compare

This patch fixes a bug in the plugin: The field option jstype = JS_STRING
would generate invalid code for optimized speed.

The problem only surfaces if the plugin parameter long_type_string
is not set and code is optimized for speed (instead of for code size).
See PR #29

Bugfix for jstype = JS_STRING field option

19 Nov 09:41
Compare
Choose a tag to compare

This patch fixes a bug in the plugin: The field option jstype = JS_STRING
would still generate an interface with a bigint property. The problem only
surfaces if the plugin parameter long_type_string is not set.
See PR #28

Bugfix for Safari 14 bigint detection

13 Nov 11:07
Compare
Choose a tag to compare

This patch fixes issue #24

Thanks to @pedelman and @pzeinlinger for the bug reports!

Bugfix for RangeError in google.protobuf.Timestamp.fromDate()

11 Nov 11:36
Compare
Choose a tag to compare

This patch fixes a bug in the method google.protobuf.Timestamp.fromDate(). See issue #22

Support protoc install on older node versions

26 Oct 11:52
Compare
Choose a tag to compare

This patch fixes issue #16.

Thanks to @Caffeinix for bringing the issue up.

Bugfix for name clash with global Error object

14 Sep 22:15
Compare
Choose a tag to compare

This patch fixes a bug in the speed-optimized generated code.
The generated code for a message named "Error" would not compile.

Thanks to @pedelman for the contribution!