Skip to content

User questions: Engine not found (tooling) #19478

Description

@millsp

Hi, you have been directed to this issue because we want to learn more about your project setup. Thanks to your answers, we will be able to better take design decisions in the future.

We'd appreciate if you could take 5 minutes to answer a few questions for us. You can write your reply directly in this issue as a comment. Copy paste these questions in your answer, leave the answer blank if you don't know.

Have you tried to copy the engine in the suggested location? Did that work?

Our error message suggested you to copy the engine somewhere. How did that go?

Which package manager are you using?

For instance npm, pnpm, or yarn. Please attach the version if you know it.

Is your workspace a monorepo setup?

Is your setup hosting multiple packages in a single workspace?

Is a bundler in use? If yes, which one?

Are you using webpack, swc, esbuild, rollup, or any other bundler?

Is a framework in use? If yes, which one?

Are you using Next.js, Next, or any other framework?

Your project uses TypeScript or just JavaScript?

Do you prefer using TypeScript or JavaScript within your project, or both?

When you saw our message, did it happen locally or in deployment?

The message was "Please help us by answering a few questions".

Where is your project deployed?

Are you deploying to Vercel, Netlify, Lambda, or something else?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions