rsocket-js packages 0.0.28 published with invalid JS.
viglucci opened this issue · comments
The following packages of rsocket-js were published with bad build output which is not valid ES5 syntax.
- rsocket-core@0.0.28
- rsocket-tcp-client@0.0.28
- rsocket-tcp-server@0.0.28
- rsocket-websocket-client@0.0.28
- rsocket-websocket-server@0.0.28
- rsocket-types@0.0.28
- rsocket-flowable@0.0.28
Please pin to 0.0.27 if this issue affect your project(s) while this issue is addressed.
The following versions have been marked as deprecated in the NPM registry with a message to pin to 0.0.27.
rsocket-core@0.0.28
rsocket-tcp-client@0.0.28
rsocket-tcp-server@0.0.28
rsocket-websocket-client@0.0.28
rsocket-websocket-server@0.0.28
rsocket-types@0.0.28
rsocket-flowable@0.0.28
The root cause of this issue has been identified as an issue with the build script failing to transpile .js files marked with @flow as valid ES5 modules. This issue was not identified until now as the issue only manifested when run on Windows. #276 addresses the issue in the build script.
Additionally, new versions of each package have been published as 0.0.29-alpha.0.
rsocket-core@0.0.29-alpha.0
rsocket-tcp-client@0.0.29-alpha.0
rsocket-tcp-server@0.0.29-alpha.0
rsocket-websocket-client@0.0.29-alpha.0
rsocket-websocket-server@0.0.29-alpha.0
rsocket-types@0.0.29-alpha.0
rsocket-flowable@0.0.29-alpha.0