Replace csv-parser with papaparse

[u12206050]

Replaces csv-parser with papaparse.

This allows for supporting better detection of separators such as ;
Value parsing also seems to be easier with papaparse.

Fixes #15874

[changeset-bot]

🦋 Changeset detected

Latest commit: ff7c6fc

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@directus/api	Minor
directus	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[DanielBiegler]

Thanks so much for the PR! ❤️

Stale

[DanielBiegler]

Yay, semicolons work now! Tested the following basic example:

"bool";"msg";"name"
true;"enabled first yea";"first"
null;"null second hello";"second"
false;"disabled third yeasssss";"third"

But skipped values are now interpreted as an empty string: "" which fails for other datatypes. In my boolean example from above if you skip the null (which is how our export does it) the import fails.

On v10.6.2 without papaparser left out values work, as they're null.

So the following works on v10.6.2 but not with this PR:

"bool","msg","name"
true,"enabled first yea","first"
,"null second hello","second"
false,"disabled third yeasssss","third"

Here is the error message you'll see:

[INTERNAL_SERVER_ERROR] insert into "titles" ("bool", "msg", "name") values ($1, $2, $3) returning "id" - invalid input syntax for type boolean: ""

Outdated

[paescuj]

With the latest changes it behaves the same as before with csv-parser, meaning it's backwards-compatible and from my point of view nothing speaks against switching to papaparse anymore.

@DanielBiegler Can you check out again?

[DanielBiegler]

Did multiple tests with multiple different configs and formats and relations and everything worked! ❤️ LGTM 🚀 🚀 🚀