You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have integrated nats.ws with Angular 12. When I set the target to ES2017 or later in tsconfig, it throws an error. Using a lower version of ES modules may prevent fully leveraging the latest ECMAScript features, potentially resulting in less efficient performance optimizations and limited utilization of new features.
./node_modules/nats.ws/esm/nats.js:7472:16 - Error: Module parse failed: Unexpected token (7472:16)
File was processed with these loaders:
./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js
./node_modules/@ngtools/webpack/src/ivy/index.js
You may need an additional loader to handle the result of these loaders.
| _asyncToGenerator(function* () {
| try {
for await (const b of _this12.transport) {
| _this12.parser.parse(b);
| }
Are there any plans to update nats.ws to support higher versions of ECMAScript?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have integrated nats.ws with Angular 12. When I set the target to ES2017 or later in tsconfig, it throws an error. Using a lower version of ES modules may prevent fully leveraging the latest ECMAScript features, potentially resulting in less efficient performance optimizations and limited utilization of new features.
Are there any plans to update nats.ws to support higher versions of ECMAScript?
Beta Was this translation helpful? Give feedback.
All reactions