express-server | 一个通过node mongodb | Runtime Evironment library

As @jonrsharpe pointed out in the comments, I was assuming that with module.exports I export the app itself, but in fact I export an object containing the app. Therefore to fix the test error, I had to simply write in my test.js:

You can send any request to the index.html as well

This should be below your already defined express routes.

actually first you need to install exprees module you can do that by typing npm install express

You need to change res.sent and res.sentFile to res.send and res.sendFile

The problem here is certainly with NPM and the packages you are trying to install rather than anything to do with Docker.

Unfortunately, I am not able to reproduce the exact error that you are facing. That could be because:

• something changed in the time between now and whenever this problem occurred;
• there are some essential details that you are not showing us.

Either way, there's a general way in which such issues are solved, which should help. But first an explanation.

NPM's package (dependency) management mechanism allows packages (dependencies) to have:

• (direct) dependencies - installed automatically with the package;
• peer dependencies - have to be manually installed by the consumer of the package.

However, NPM does not allow multiple versions of the same package to coexist.

Also, as you may know, packages use standard semantic versioning, which means that a major version change indicates a breaking change.

Due to these two reasons, clashes occur if one package requires dependency A to be v1, while another wants the same dependency A to be v2.

NPM v7 was recently released and this is the version that current (as of November 2020) node:current images use.

Probably the biggest changes brought about by NPM7 relate to peer dependencies - NPM should now be able to install them automatically, if possible. Read more here.

As described in the document, in cases where it's not possible to solve the conflicts, NPM should now throw errors rather than warnings, which is what you are seeing.

I, on the other hand, only managed to get warnings and no errors using your setup and NPM v7.0.8, and I don't know why. The problems reported were essentially the same, however, so the resolution ought to be very similar.

The only solution that I'm aware of is manual conflict resolution - the developer needs to adjust their dependencies to play along.

In your specific case the problem seems to be with the graphql package. The latest graphql package is v15, which is also a peer dependency of the latest type-graphql package (v1).

However, apollo-server-express has a few dependencies, which apparently only support graphql up to and including v14.

While you wait for apollo-server-express to fully support v15, you may opt for graphql v14 altogether by downgrading the only package that requires v15. So if you change your npm install to this:

I'll Post the answer here.

Add this module: npm i esm

Add one more file under the root folder I'll name it as main.js:

You cannot host a node.js app in most providers working with cpanel. If you want to host a node.js app you should deploy it on a vps. You can follow this tutorial for example: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-16-04

But in these cpanel providers, you could host a static react app (for example an app build with create-react-app). This kind of app does not need node.js at runtime. So you can build the assets and push them to your cpanel host.

You can follow this tutorial: https://dev.to/crishanks/deploy-host-your-react-app-with-cpanel-in-under-5-minutes-4mf6

The --delay option should help (docs).

Try something like (untested):

This error is caused by multiple NgModules in the app.module, as the first NgModule imports doesn't contain BrowserModule.

app would still work fine if you remove first NgModule since the modules in the imports are already imported in the second one