d3-dsv | A parser and formatter for delimiter-separated values | CSV Processing library

At the moment you are passing an array of all the years

Use d3.tsv with the promise-based API. Since your file is very large, one optimisation we can do is instead of doing a for-each on each element after they get parsed by D3, use the loop done at parsing time via the initialization function:

Firstly, make sure you are copying the same package-lock.json file that you use to install deps locally, to make sure you have the same dependency tree in your container as you do locally.

COPY package.json package-lock.json /app/

Then, make sure that you are matching the same node/npm version as you run locally (replace 12 with the major version you are running, be it 10, 12, 14 or whatever):

FROM node:12

Each node version is bundled with a specific npm version (latest 12 version comes with npm 6.14.6), you can find the bundled NPM version int he changelogs, https://github.com/nodejs/node/tree/master/doc/changelogs

Additionally, instead of running npm install, you might wanna run npm ci in the container. The latter skips any checks for discrepancy between the lock file and your package.json file and just installs the locked dependency tree, which is not only faster, but will also match your local dep tree exactly.

EDIT:

In addition, this line:

COPY . /app

Would also overwrite node_modules unless you have ignored it via .dockerignore or similar.

Easiest would probably be to add a .dockerignore file to the same folder as your Dockerfile and add lines stating:

I was able to get this by adding the following code below where I was adding the line:

Node.js doesn't get bundled with the source code of apps. The package.json might have a section called "engines" in which it will state what version you should be using.

If the root package.json doesn't have the "engines" section, then it may be posable that the some of the dependencies do say which version they require to be used. It would be kind of annoying going through each one to check, so a good way would be just to download a version of Node and run npm install. If everything works, then you know that the Node version the app was created in is most likely older (its a bit tedious, I know).

Another thing you could look for (but might not be to helpful) would be to check when the files of the source code were created (especially the package.json file), and find the Node version that was released around that time. This wont be as accurate as the first method but it will give you a working version of Node.

When it comes down to it though, its probably always best to use the most up to date version (or the most recent LTS version) as they come with all the latest security patches and improvements.

Use d3.csv("data.csv", function(data){...}) to get CSV from url and parse, or use d3.csv.parse() to parse a CSV-formatted string.

Determined the cause of the problem. The callback along with getAddressed needs to be returned.

You probably don't need this line in your component.ts file (It's only for Angular <6):

Seems, this issue due to update

https://www.npmjs.com/package/@types/d3-dsv/v/0.4.4?activeTab=versions

I have this problem too.

Try to fix lib version to 1.0.31 in your package.json