I am tryin to use Server sent events in NestJs as per:
here
However when tryint to import
import { Sse } from '#nestjs/common';
I get:
Module '"../../../../node_modules/#nestjs/common"' has no exported member 'Sse'.ts(2305)
nest info tells me:
[System Information]
OS Version : Windows 10
NodeJS Version : v12.11.1
NPM Version : 6.11.3
[Nest CLI]
Nest CLI Version : 6.14.2
[Nest Platform Information]
platform-express version : 6.11.11
passport version : 6.2.0
graphql version : 6.6.2
typeorm version : 6.3.4
common version : 6.11.11
core version : 6.11.11
jwt version : 6.1.2
This solved the issue:
Nest CLI Version : 6.14.2
does NOT support SSE;
Upgrade to version: 7.5.2 +
Related
I am currently working on a jhipster project.
I had to encounter some difficulties with jhipster translation-not-found[error.url.not.found],
that I was able to solve and I would like to share the result of my research.
here is my problem in a few pictures.
After refreshing the page, the credentials no longer work
Infos :
jhipsterVersion: 6.10.5
applicationType: monolith
clientFramework: angularX
Environment and Tools
java version "11.0.12" 2021-07-20 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.12+8-LTS-237)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.12+8-LTS-237, mixed mode)
git version 2.15.0
node: v12.16.1
npm: 6.13.4
Docker version 20.10.7, build f0df350
docker-compose version 1.29.2, build 5becea4c
Resolution,
The problem is due to the high size of the headers at the FRONT (Angular) and BACKEND (Spring-boot) level.
1- FRONT correction :
Edit package.json (Edit the package.json file and add the following parameter On title webpack-dev-server and webpack : --max-http-header-size=102400000)
2- BACKEND correction :
Edit application.propertie files (application-dev.yml and application-prod.yml), add : server.max-http-header-size: 102400000
I humbly hope this helps you
Translator: Google translate
I am trying to find to see if expressjs 4 can support Nodejs 10.15.3 ( Lts) version. Is there any compatibility matrix that i can look into before deciding versions to choose?
If you check out express/package.json you can see that express needs node v0.10.0 or newer.
So yes, Express.js v4 is supporting Node.js v10.15.3.
So this is really strange.
Local dev environment :
OS : Win x64
Node version : 8.x (LTS)
The project does not build with the AOT flag. It throws "xyz" does not exist in object of type {}.The fix to this is very obvious.
Remote env:
OS : linux x64
Node version : 6.x (LTS)
The project builds successfully without the above-mentioned compiler errors!
Both environments have the same CLI version. The only difference being the node version, local being higher.
Can anyone shed some light on this? Does the compiler behave differently on node versions higher than 6.x LTS?
ConfigurationError: Server at xxxxx:27017 reports wire version 0, but this version of nodejs requires at least 2 (MongoDB 2.6).
I had the same issue using Linux subsystem for Windows and Nodejs mongoose v5.0.7.
I solved the issue by upgrading my MongoDB to v3.6.3 following the instructions on their documentation page. Install docs here.
Hope it helps.
I installed couchdb on my VM
vm version : Red Hat 4.4
couchdb version : 1.6.1
spidermonkey version : 1.8.5
erlang version : R16B02
When I try to run a view, the log non-stop prints this error, just this message
enter image description here