Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

@parcel/ts-utils does not work on node without es module support

See original GitHub issue

🐛 bug report

@parcel/ts-utils does not work on node without es module support.

🎛 Configuration (.babelrc, package.json, cli command)

.parcelrc

{
  "extends": [
    "@parcel/config-default"
  ],
  "transforms": {
    "*.ts": [
      "@parcel/transformer-typescript-tsc"
    ],
    "*.tsx": [
      "@parcel/transformer-typescript-tsc"
    ]
  }
}

🤔 Expected Behavior

The project compiles successfully.

😯 Current Behavior

Node emits an error in script of @parcel/ts-utils.

💁 Possible Solution

Emit code with commonjs modules on package @parcel/ts-utils.

🔦 Context

Node emits the following error:

 Error: Unexpected token 'export'
~/node_modules/@parcel/ts-utils/src/index.js:2
export * from './FSHost';
^^^^^^

SyntaxError: Unexpected token 'export'
    at wrapSafe (internal/modules/cjs/loader.js:1043:16)
    at Module._compile (internal/modules/cjs/loader.js:1091:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1160:10)
    at Module.load (internal/modules/cjs/loader.js:976:32)
    at NodePackageManager.load (~/node_modules/@parcel/package-manager/lib/NodePackageManager.js:106:9)
    at NodePackageManager.requireSync (~/node_modules/@parcel/package-manager/lib/NodePackageManager.js:72:17)
    at Module.m.require (~/node_modules/@parcel/package-manager/lib/NodePackageManager.js:93:19)
    at require (internal/modules/cjs/helpers.js:69:18)
    at Object.<anonymous> (~/node_modules/@parcel/transformer-typescript-tsc/lib/TSCTransformer.js:10:16)
    at Module._compile (internal/modules/cjs/loader.js:1121:30)

tsconfig.json

{
  "compilerOptions": {
    "incremental": true,
    "target": "es5",
    "module": "commonjs",
    "jsx": "react",
    "rootDir": "./src",

    "strict": true,

    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,

    "esModuleInterop": true,

    "forceConsistentCasingInFileNames": true,

    "baseUrl": "./src",
    "paths": {
      "~*": ["./*"]
    }
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules"]
}

💻 Code Sample

https://github.com/xfoxfu/parcel-issue-3931

🌍 Your Environment

Software	Version(s)
Parcel	2.0.0-alpha.3.2
Node	13.4.0
npm/Yarn	1.19.2
Operating System	macOS 10.15.2

Issue Analytics

State:
Created 4 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

2reactions

saint-justincommented, Aug 17, 2021

Ok the problem was that it used alpha version of the @parcel/transformer-typescript-tsc package instead of ^2.0.0-beta.3.1. Just leaving it here if someone have similar problem.

Had the same issue as @lukejagodzinski, the command below solved the problem for me too for anyone else running into this. Make sure this is the right version for you if you’re a person from the future.

npm i --save-dev @parcel/transformer-typescript-tsc@^2.0.0-beta.3.1

2reactions

lukejagodzinskicommented, Jun 20, 2021

Ok the problem was that it used alpha version of the @parcel/transformer-typescript-tsc package instead of ^2.0.0-beta.3.1. Just leaving it here if someone have similar problem.