Error parsing triggers: Cannot find module 'csv-parse/sync' #323

appfrilans · 2022-02-22T17:23:14Z

Describe the bug

When I try to use csv-parse/sync instead of csv-parse, my deploy to Firebase Functions fail with the following error:

Error: Error parsing triggers: Cannot find module 'csv-parse/sync''
Require stack:
- /Users/xxx/Programming/xxx/Firebase Functions/xxx/functions/lib/index.js
- /usr/local/lib/node_modules/firebase-tools/lib/deploy/functions/runtimes/node/triggerParser.js

Try running "npm install" in your functions directory before deploying.

To Reproduce

Import using:

import { parse } from 'csv-parse/sync';

Then use in code like this:

interface EventData {
	update: string;
	id: string;
	title: string;
	description: string;
	category: string;
	ages: string;
	place: string;
	placeCoordinate: string;
	startDate: string;
	startTime: string;
	length: string;
	url: string;
	arrName: string;
  }


let events: Array<EventData> = []
const headers = ["update", "id", "title", "description", "ages", "place", "placeCoordinate", "startDate", "startTime", "length", "url", "arrEpost", "arrName", "validated", "skugg"]
try {
    events = parse(text, {columns: headers, from: 6, quote: "\"", delimiter: ";", ltrim: true, rtrim: true})
}...

I have installed by going to /functions-folder and running

npm install --save csv-parse

Deploying in root folder with

firebase deploy

Additional context

Is this an issue with the framework, with firebase or am I doing something wrong? Normal use of "csv-parse" without sync works just fine.

The text was updated successfully, but these errors were encountered:

wdavidw · 2022-02-22T18:17:24Z

I have never used firebase so I might pass on this one.

appfrilans · 2022-02-23T07:44:56Z

Ok. Posted a similar question on SO: https://stackoverflow.com/questions/71232999/error-parsing-triggers-cannot-find-module-csv-parse-sync

froesecom · 2022-02-28T21:58:42Z

I have a similar issue outside of firebase in a plain TypeScript script using version 5.0.4

karlhorky · 2022-03-08T19:03:54Z

Edit: Jest 28 no longer has this issue: #323 (comment)

Version 6.0.5 is also throwing an error with Jest 27 Experimental ESM support + Node v16.11.0 (ESM):

package.json

{
  "type": "module",
  "dependencies": {
    "csv": "6.0.5"
  },
  "scripts": {
    "test": "NODE_OPTIONS=--experimental-vm-modules npx jest"
  },
  "jest": {
    "transform": {},
  }
}

index.test.js (import copied from the docs)

import {generate, parse, transform, stringify} from 'csv/sync';

test('empty test', () => {});

Running npm test yields:

$ /Users/k/projects/project/node_modules/.bin/jest
(node:27879) ExperimentalWarning: VM Modules is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 FAIL  __tests__/index.test.js
  ● Test suite failed to run

    Cannot find module 'csv/sync' from 'index.js'

      at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.144 s, estimated 1 s
Ran all test suites.

Workaround for Jest (throws in Node.js):

import { parse, stringify } from 'csv/dist/esm/sync';

Throws this error in Node.js:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/esm/sync' is not defined by "exports" in /Users/k/projects/changes-codealong/node_modules/csv/package.json imported from /Users/k/projects/changes-codealong/index.js
    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:440:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:692:3)
    at packageResolve (node:internal/modules/esm/resolve:873:14)
    at moduleResolve (node:internal/modules/esm/resolve:929:18)
    at Loader.defaultResolve [as _resolve] (node:internal/modules/esm/resolve:1044:11)
    at Loader.resolve (node:internal/modules/esm/loader:89:40)
    at Loader.getModuleJob (node:internal/modules/esm/loader:242:28)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)
    at link (node:internal/modules/esm/module_job:75:36) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Workaround for both Jest and Node.js:

import { parse, stringify } from './node_modules/csv/dist/esm/sync.js';

bnwa · 2022-03-12T01:26:29Z

Am getting the same issue as others have reported attempted to bind dep with import { parse } from 'csv-parse/sync'

Version 6.0.5 is also throwing an error with Jest 27 Experimental ESM support + Node v16.11.0 (ESM):

package.json

{
  "type": "module",
  "dependencies": {
    "csv": "6.0.5"
  },
  "scripts": {
    "test": "NODE_OPTIONS=--experimental-vm-modules npx jest"
  },
  "jest": {
    "transform": {},
  }
}

index.test.js (import copied from the docs)

import {generate, parse, transform, stringify} from 'csv/sync';

test('empty test', () => {});

Running npm test yields:

$ /Users/k/projects/project/node_modules/.bin/jest
(node:27879) ExperimentalWarning: VM Modules is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 FAIL  __tests__/index.test.js
  ● Test suite failed to run

    Cannot find module 'csv/sync' from 'index.js'

      at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.144 s, estimated 1 s
Ran all test suites.

Workaround for Jest (throws in Node.js):

import { parse, stringify } from 'csv/dist/esm/sync';

Throws this error in Node.js:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/esm/sync' is not defined by "exports" in /Users/k/projects/changes-codealong/node_modules/csv/package.json imported from /Users/k/projects/changes-codealong/index.js
    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:440:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:692:3)
    at packageResolve (node:internal/modules/esm/resolve:873:14)
    at moduleResolve (node:internal/modules/esm/resolve:929:18)
    at Loader.defaultResolve [as _resolve] (node:internal/modules/esm/resolve:1044:11)
    at Loader.resolve (node:internal/modules/esm/loader:89:40)
    at Loader.getModuleJob (node:internal/modules/esm/loader:242:28)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)
    at link (node:internal/modules/esm/module_job:75:36) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Workaround for both Jest and Node.js:

import { parse, stringify } from './node_modules/csv/dist/esm/sync.js';

Workaround only gets me this:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /Users/b/Source/project/node_modules/csv-parse/dist/esm/sync.js require() of ES modules is not supported. require() of /Users/b/Source/project/node_modules/csv-parse/dist/esm/sync.js from /Users/b/Source/project/conversion/src/csv.ts is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules. Instead rename sync.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /Users/b/Source/project/node_modules/csv-parse/package.json.

karlhorky · 2022-03-12T11:47:07Z

Workaround only gets me this

@bnwa check inside your node_modules folder - I think there is a non-ESM version of the file.

Should be in the node_modules/csv-parse/dist folder, but NOT in the esm folder - look through the other folders for a CommonJS version

bnwa · 2022-03-12T16:02:30Z

Workaround only gets me this

@bnwa check inside your node_modules folder - I think there is a non-ESM version of the file.

Should be in the node_modules/csv-parse/dist folder, but NOT in the esm folder - look through the other folders for a CommonJS version

Using require and passing the CommonJS path from the dist dir in node_modules worked instead of the ESM dir with import. I thought ts-node was transforming ESM import/export before evaluating deps. Thanks for the tip.

karlhorky · 2022-03-12T16:34:46Z

Nice! I guess it should also work with import, using the CommonJS path - in case you prefer that to require.

bnwa · 2022-03-12T16:39:22Z

Nice! I guess it should also work with import, using the CommonJS path - in case you prefer that to require.

TS won't match the declaration file when called with ESM syntax for whatever reason

karlhorky · 2022-04-28T19:50:46Z

Version 6.0.5 is also throwing an error with Jest 27 Experimental ESM support + Node v16.11.0 (ESM)
import {generate, parse, transform, stringify} from 'csv/sync';
// ...

This is no longer throwing on Jest 28 🎉 Thanks to support for the exports field in package.json.

So the version from the docs can now be used with Jest. (although due to import-js/eslint-plugin-import#1810 it is still incompatible with eslint-plugin-import's no-unresolved rule)

vladimirpetukhov · 2022-08-08T16:14:42Z

I have this problem on Expressjs app node version 12+, and also run the project with node 10, 12 , 14 ,16.What I tried:

With versions 5.0.4 and 5.3.0
import parse from 'csv-parse/dist/esm/sync';
import parse from 'csv-parse/lib/sync';
Result: error TS2349: This expression is not callable. const records = parse(fileContent, {

import {parse} from 'csv-parse/dist/esm/sync';
import {parse } from 'csv-parse/lib/sync';
export { CsvError, parse };
^^^^^^

SyntaxError: Unexpected token export

import {parse } from 'csv-parse/sync';
[INFO] ts-node-dev ver. 1.1.8 (using ts-node ver. 9.1.1, typescript ver. 4.5.4)
Error: Cannot find module 'csv-parse/sync'

tfazekas · 2022-08-10T08:11:04Z

As you can see in the csv-parse package.json file the lib/sync is exported ./sync, so you will be able to import lib/sync like this:

import { parse } from 'csv-parse/sync';

// ... 
"exports": {
    ".": {
      "import": "./lib/index.js",
      "require": "./dist/cjs/index.cjs",
      "types": "./lib/index.d.ts"
    },
    "./sync": {
      "import": "./lib/sync.js",
      "require": "./dist/cjs/sync.cjs",
      "types": "./lib/sync.d.ts"
    },
    "./browser/esm": {
      "types": "./lib/index.d.ts",
      "default": "./dist/esm/index.js"
    },
    "./browser/esm/sync": {
      "types": "./lib/sync.d.ts",
      "default": "./dist/esm/sync.js"
    }
// ...

yellowmamba · 2022-11-15T23:43:51Z

This is still an issue...

Using latest version 5.3.2 On node 14:

If you do

import { parse } from "csv-parse/sync"

You get

Error: Cannot find module 'csv-parse/sync'

If you do

import { parse } from "csv-parse/lib/sync"

You get

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /<path>/node_modules/csv-parse/lib/sync.js
require() of ES modules is not supported.
require() of /<path>/node_modules/csv-parse/lib/sync.js from <my-script> is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename sync.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /<path>/node_modules/csv-parse/package.json.

To help with debugging, this is my script's package.json

{
  "name": "my-package",
  "version": "0.1.0",
  "dependencies": {
    "csv-parse": "^5.3.2",
  }
}

wdavidw · 2022-11-16T17:09:49Z

This is a nightmare

shunyun-bp · 2023-08-11T14:22:50Z

Had a related problem compiling with pkg. TS using modules would work using require("csv/sync") but pkg cannot find the module. Using require("csv/dist/cjs/sync.cjs") works for compiling but TS rejects, complaining it can't find the module.
Finally able to use both TS and pkg for this by using
var { generate, parse, transform, stringify } = require("../../node_modules/csv/dist/cjs/sync.cjs");
That is, using this in a .ts ESM file works for build (for dev/debug) and compiling.

karlhorky · 2023-08-21T16:55:00Z

@wdavidw maybe this is actually a problem in the published version of csv-parse (and other packages) - check out the error report below from Are the types wrong? by @andrewbranch

(this also happens for csv-generate, and may affect other node-csv packages)

Internal resolution error

Import found in a type declaration file failed to resolve. Either this indicates that runtime resolution errors will occur, or (more likely) the types misrepresent the contents of the JavaScript files.

andrewbranch · 2023-08-21T18:03:42Z

Yeah, if you expand the details, you can see the problem.

fileName: "/node_modules/csv-parse/dist/cjs/sync.d.cts"
moduleSpecifier: "./index.js"

but that directory doesn’t contain an index.js; it contains an index.cjs. https://unpkg.com/browse/csv-parse@5.4.0/dist/cjs/

MaximeBernard · 2023-08-22T14:15:10Z

Pretty sure it comes from packages/csv-parse/rollup.config.js but I've never used Rollup so I might be wrong. Any Rollup expert over here?

wdavidw · 2023-08-24T10:33:48Z

Could you check the latest version 5.4.1 with Are types wrong ?, the "csv-parse/sync" with node16 from CJS is now ok after the changes from #397.

karlhorky · 2023-08-25T10:57:53Z

Hm, I just tried upgrading to csv@6.3.2 (which also includes the changes from #397) and I no longer need an ESLint disable for import/no-unresolved (not sure if this was caused by this change or some other earlier change) - can anyone else confirm that this is fixed now?

MaximeBernard · 2023-08-25T14:32:03Z

Still have the issue. Eslint is looking for "/node_modules/csv-parse/dist/esm/sync" instead of "/node_modules/csv-parse/lib/sync". This is weird because the package.json looks correct.

I'm using TypeScript btw. Is it only a TS issue?

Is it just me?

nklemiata · 2024-01-11T21:35:11Z

Still have the issue. Eslint is looking for "/node_modules/csv-parse/dist/esm/sync" instead of "/node_modules/csv-parse/lib/sync". This is weird because the package.json looks correct.

I'm using TypeScript btw. Is it only a TS issue?

Is it just me?

Me too, with TS and csv-parse. And I don't want to install whole csv@6.3.2 just to parse a small .csv because of these errors...
Made it work with an awkward mix of ESM & CJS:
import { parse } from "../../node_modules/csv-parse/dist/cjs/sync.cjs";
based on @shunyun-bp answer above.

ueokande mentioned this issue Aug 15, 2022

refactor: refactor CSV printer kintone/cli-kintone#33

Merged

5 tasks

davebeyer mentioned this issue Apr 12, 2023

Package subpath './lib/sync' is not defined by "exports" in ... csv-stringify/package.json #385

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error parsing triggers: Cannot find module 'csv-parse/sync' #323

Error parsing triggers: Cannot find module 'csv-parse/sync' #323

appfrilans commented Feb 22, 2022 •

edited

Loading

wdavidw commented Feb 22, 2022

appfrilans commented Feb 23, 2022

froesecom commented Feb 28, 2022

karlhorky commented Mar 8, 2022 •

edited

Loading

bnwa commented Mar 12, 2022

karlhorky commented Mar 12, 2022

bnwa commented Mar 12, 2022 •

edited

Loading

karlhorky commented Mar 12, 2022

bnwa commented Mar 12, 2022

karlhorky commented Apr 28, 2022

vladimirpetukhov commented Aug 8, 2022

tfazekas commented Aug 10, 2022

yellowmamba commented Nov 15, 2022 •

edited

Loading

wdavidw commented Nov 16, 2022

shunyun-bp commented Aug 11, 2023

karlhorky commented Aug 21, 2023

andrewbranch commented Aug 21, 2023

MaximeBernard commented Aug 22, 2023

wdavidw commented Aug 24, 2023 •

edited

Loading

karlhorky commented Aug 25, 2023 •

edited

Loading

MaximeBernard commented Aug 25, 2023

nklemiata commented Jan 11, 2024 •

edited

Loading

Error parsing triggers: Cannot find module 'csv-parse/sync' #323

Error parsing triggers: Cannot find module 'csv-parse/sync' #323

Comments

appfrilans commented Feb 22, 2022 • edited Loading

wdavidw commented Feb 22, 2022

appfrilans commented Feb 23, 2022

froesecom commented Feb 28, 2022

karlhorky commented Mar 8, 2022 • edited Loading

bnwa commented Mar 12, 2022

karlhorky commented Mar 12, 2022

bnwa commented Mar 12, 2022 • edited Loading

karlhorky commented Mar 12, 2022

bnwa commented Mar 12, 2022

karlhorky commented Apr 28, 2022

vladimirpetukhov commented Aug 8, 2022

tfazekas commented Aug 10, 2022

yellowmamba commented Nov 15, 2022 • edited Loading

wdavidw commented Nov 16, 2022

shunyun-bp commented Aug 11, 2023

karlhorky commented Aug 21, 2023

andrewbranch commented Aug 21, 2023

MaximeBernard commented Aug 22, 2023

wdavidw commented Aug 24, 2023 • edited Loading

karlhorky commented Aug 25, 2023 • edited Loading

MaximeBernard commented Aug 25, 2023

nklemiata commented Jan 11, 2024 • edited Loading

appfrilans commented Feb 22, 2022 •

edited

Loading

karlhorky commented Mar 8, 2022 •

edited

Loading

bnwa commented Mar 12, 2022 •

edited

Loading

yellowmamba commented Nov 15, 2022 •

edited

Loading

wdavidw commented Aug 24, 2023 •

edited

Loading

karlhorky commented Aug 25, 2023 •

edited

Loading

nklemiata commented Jan 11, 2024 •

edited

Loading