When trying to load kokoro-js with nextjs

[ayushpaharia]

Link to the code that reproduces this issue

https://github.com/ayushpaharia/kokoro-web-worker

To Reproduce

Install using
npm install

packages inluded
kokoro-js motion

Run using
npm run dev

Current vs. Expected behavior

Current Behaviour:

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./pages/worker.js
./pages/index.tsx
AMP bind syntax [0-9]='' is not supported in JSX, use 'data-amp-bind-0-9' instead. https://nextjs.org/docs/messages/amp-bind-jsx-alt
Warning: data for page "/_error" (path "/") is 6.45 MB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
 GET / 500 in 9867ms

Expected Behavior: (As I've seen in this example)
Kokoro JS Vite Demo

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #53-Ubuntu SMP PREEMPT_DYNAMIC Sat Jan 11 00:06:25 UTC 2025
  Available memory (MB): 15675
  Available CPU cores: 16
Binaries:
  Node: 22.9.0
  npm: 10.8.3
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.2.0-canary.33 // Latest available version is detected (15.2.0-canary.33).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: standalone

Which area(s) are affected? (Select all that apply)

create-next-app, Package Managers, React, Runtime, Webpack

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

Additional context

I'm trying to setup kokoro-js locally the TTS model to run in browser but I'm getting issues with getting the module to load.
It works fine with vite so I'm not sure what the issue is here. I've tried using directly in my client and also in a webworker but it doesn't work

Although when I tried using kokoro-js via api endpoint it works.

I'm trying to get it to run in the browser so that's not an option.

Issue also posted on kokoro-js repo
Issue

[github-actions]

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the please add a complete reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

If you cannot create a clean reproduction, another way you can help the maintainers' job is to pinpoint the canary version of next that introduced the issue. Check out our releases, and try to find the first canary release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next by running npm install next@<version>.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 2 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[ayushpaharia]

@samcx, I've removed unecessary dependencies.

Here is a live working example which was build from Vite:
Example

More info regarding steps to reproduce.

npm i kokoro-js (a text-to-speech model which was build on an abstraction with transformers-js)
kokoro-js
transformers-js with next

The output:

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./pages/worker.js
./pages/index.tsx
AMP bind syntax [0-9]='' is not supported in JSX, use 'data-amp-bind-0-9' instead. https://nextjs.org/docs/messages/amp-bind-jsx-alt
Warning: data for page "/_error" (path "/") is 6.45 MB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
 GET / 500 in 4555ms

Logs in browser console:

GET http://localhost:3000/ 500 (Internal Server Error)
Navigated to http://localhost:3000/

Network tab:

Please suggest anything that I might have been missing. I'd really like to crack this issue.