node v17: Error loading `tslib` helper library

[aladdin-add]

What happens and why it is wrong

Error loading `tslib` helper library.
/Users/weiran/repo/dian/tsdx/node_modules/rollup-plugin-typescript2/dist/rollup-plugin-typescript2.cjs.js:25177
    throw e;
    ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './package.json' is not defined by "exports" in /Users/weiran/repo/dian/tsdx/node_modules/rollup-plugin-typescript2/node_modules/tslib/package.json

Environment

Versions

  Node: 17.0.0
  OS: macOS 12.0
  yarn: 3.0.2

   rollup: ^2.57.0 => 2.58.0 
    rollup-plugin-typescript2: ^0.30.0 => 0.30.0 
    typescript: ^4.4.3 => 4.4.4

rollup.config.js

`rollup.config.js`:

tsconfig.json

`tsconfig.json`:

package.json

`package.json`:

plugin output with verbosity 3

plugin output with verbosity 3:

[aladdin-add]

this is from weiran-zsd/dts-cli#78.

[yoeunes]

Hello @aladdin-add did you find any solution for this error ? I got it also with node 17

  Node: v17.0.1
  npm: 8.1.0
  OS: Ubuntu
  rollup: 2.58.0
 rollup-plugin-typescript2: 0.30.0

[aladdin-add]

1. just down to node < 17
2. yarn resolutions:

"resolutions":{
  "tslib": "2.3.1"
}

[yoeunes]

thank you

[xiCO2k]

Checking in on this, any updates?

[bluelovers]

Checking in on this, any updates?

i think my pr can fix this

[bluelovers]

can try this before merge apply

"rollup-plugin-typescript2": "bluelovers/rollup-plugin-typescript2#pr/node-v17-tslib-002",

[ezolenko]

@bluelovers I'm having trouble building with node 17 (unrelated to your PR), because something breaks semver either at runtime (before upgrading commonjs plugin) or at build time, so I had to disable version check. Do you see those problems at all?

See this commit, which is basically your PR but with any changes needed to upgrade: cb2621f

I used normal resolve (stole it from rollup-plugin-typescript):

import resolve from "resolve";
const tslibPath = resolve.sync("tslib/tslib.es6.js");

Is your approach with @yarn-tool/resolve-package significantly better?

[bluelovers]

u need build at node.js 16, and disable version test before publish new version once

after this, enable ur version test will work

[aladdin-add]

a workaround: if you are using docker, you can change the node:latest => node:lts(or node:16/14) to avoid the error.