Import error

[elie222]

Getting this error:

Cannot find module 'frames.js/next/server' or its corresponding type declarations.ts(2307)

When doing:

export { POST } from "frames.js/next/server";

Next.js project. Anything I need to add to fix it?

[elie222]

And probably related, is this runtime error:

TypeError: module1.render is not a function

Do I need adjust my tsconfig to get it to work? The starter kit does work for me but I'm adding this to an existing repo.

[stephancill]

@elie222 would you mind sharing a reproducible example?

[davidfurlong]

Do I need adjust my tsconfig to get it to work? The starter kit does work for me but I'm adding this to an existing repo.

looks like a tsconfig issue - we're exporting both CJS and ESM modules but haven't rigorously tested CJS. Mind posting your config?

[elie222]

Here you go:

{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "sourceMap": true,
    "outDir": "dist",
    "baseUrl": ".",
    "paths": {
      "@utils/*": ["utils/*"],
      "@components/*": ["components/*"],
      "@app/*": ["app/*"],
      "@pages/*": ["pages/*"],
      "@api/*": ["pages/api/*"],
      "@hooks/*": ["hooks/*"],
      "@layouts/*": ["layouts/*"],
      "@providers/*": ["providers/*"],
      "@images/*": ["images/*"],
      "@validations/*": ["validations/*"],
      "@emails/*": ["emails/*"]
    },
    "plugins": [
      {
        "name": "next"
      }
    ]
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules", "cypress"]
}

[stephancill]

@elie222 I'm able to reproduce the issue on my side. Seems to be related to the "moduleResolution": "Node" compiler option in your tsconfig. Changing it to "NodeNext" solved it for me (also required you to modify "module": "NodeNext"). If you're not willing or able to do that, a workaround is to import directly from frames.js/dist/next/server e.g.

export { POST } from "frames.js/dist/next/server";

[elie222]

@elie222 I'm able to reproduce the issue on my side. Seems to be related to the "moduleResolution": "Node" compiler option in your tsconfig. Changing it to "NodeNext" solved it for me (also required you to modify "module": "NodeNext"). If you're not willing or able to do that, a workaround is to import directly from frames.js/dist/next/server e.g.

export { POST } from "frames.js/dist/next/server";

This worked. Thanks!

[stephancill]

You're welcome!

[elie222]

```ts
export { POST } from "frames.js/dist/next/server";

My bad, this doesn't work:

export { POST } from https://github.com/framesjs/frames.js;

I'd keep this issue open tbh to avoid people having to use workarounds.

[stephancill]

Can you elaborate on the problem you're facing? What is the error?

[davidfurlong]

Thanks @elie222 you're right - this is an issue on our end; https://arethetypeswrong.github.io/?p=frames.js%400.4.3
node 10 is having problems with the types, looking at it

[gomesalexandre]

@davidfurlong if this can help, finally found what was wrong on my end trying to run the starter example - since this is a monorepo, yarn needs to be ran first at the root of the repo. I noticed that running yarn first in the framesjs-starter would install frames.js without building it.

Since the build is done on prepublish hook, that makes sense, in other words, the example script won't run if cloning the repo. I'd assume this is a common issue, since most wouldn't think about moving the folder somewhere else and git initing it as its own repo.

#76

[davidfurlong]

@davidfurlong if this can help, finally found what was wrong on my end trying to run the starter example - since this is a monorepo, yarn needs to be ran first at the root of the repo. I noticed that running yarn first in the framesjs-starter would install frames.js without building it.

Since the build is done on prepublish hook, that makes sense, in other words, the example script won't run if cloning the repo. I'd assume this is a common issue, since most wouldn't think about moving the folder somewhere else and git initing it as its own repo.

#76

Thank you! I don't think it'll fix this issue though

[elie222]

Thanks @elie222 you're right - this is an issue on our end; arethetypeswrong.github.io/?p=frames.js%400.4.3 node 10 is having problems with the types, looking at it

Who uses Node 10?