Entry point 'ngx-papaparse' contains deep imports using Angular 9 about ngx-papaparse

[alberthaff]

Please check your package-lock.json instead. The package.json file doesn't necessarily reflect what's installed.

AFAIK, the CommonJS warning should not appear until NG10. However, if you are using ivy, it may actually do.
Please try this and see if it solves the problem: https://alberthaff.dk/projects/ngx-papaparse/docs/v5/installation/angular-10-or-later

If so, i'll update the docs to also reflect ivy users in NG9.

[gitalvininfo]

Closing this issue. My fault.
Its actually one of my dev dependency that causes this warning which is @angular-devkit/build-angular ^0.1001.6 . I just trace my previous version for this dev dependency then everything works fine.

In case of Ivy, I did not disable it and just leave it to default (which is enabled) and I think, this is nothing to do with Ivy IMO.
I remember I run a command to clean cache for npm and hit npm install and this might cause the accidental update of my dev dependency.

Anyways thanks for telling me that package-lock.json must be checked first instead of the package.json.

[alberthaff]

Which version of ngx-papaparse are you using?
https://alberthaff.dk/projects/ngx-papaparse/docs/v5

You can choose between version in the upper left corner. Each version is only compatible with the stated Angular versions.

[gitalvininfo]

Im sorry I forgot, but I used the current ngx-papaparse right now which is 5.0.0 and Angular 9.0.7.

I don't actually know what is the cause for this issue.

This is the another warning after I run again ng serve

Here is my package.json

[alberthaff]

Are you sure that you aren't using Angular 10?
Try reading this: https://alberthaff.dk/projects/ngx-papaparse/docs/v5/installation/angular-10-or-later

[gitalvininfo]

Im 300% sure that Im not using Angular 10 😕.
Yes Ive seen this solution which ignores the warning if you are using Angilar 10

This is my package.json for my version of angular

Here is my dev dependency

Im confused as to why is this even happening since Im on Angular 9.