You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're trying to make our typechain types reuseable by packaging them up as a private npm package. However this seems to cause issues like the following when in use in nextjs.
./node_modules/@scopeName/packageName/index.ts
Module parse failed: Unexpected token (6:12)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| /* eslint-disable */
> import type * as openzeppelin from "./@openzeppelin";
| import type * as uniswap from "./@uniswap";
| import type * as contracts from "./contracts";
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're trying to make our typechain types reuseable by packaging them up as a private npm package. However this seems to cause issues like the following when in use in nextjs.
Here's the package.json for the package:
The root of the package is the output dir of typechain, containing all the types as well as the copied artifacts dir from hardhat.
I've seen a few related issues to this but no resolution yet #609 (comment) #278 (comment) , would be great to get some guidance here or a fix.
We're using
"@typechain/ethers-v5": "^10.0.0",
Beta Was this translation helpful? Give feedback.
All reactions