Thanks to visit codestin.com
Credit goes to github.com

Skip to content

hls.js doesn't contain default export in "app" router #57809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
maybephilipp opened this issue Oct 31, 2023 · 2 comments
Closed
1 task done

hls.js doesn't contain default export in "app" router #57809

maybephilipp opened this issue Oct 31, 2023 · 2 comments
Labels
bug Issue was opened via the bug report template. stale The issue has not seen recent activity.

Comments

@maybephilipp
Copy link

maybephilipp commented Oct 31, 2023 •
edited
Loading

Link to the code that reproduces this issue

https://github.com/maybephilipp/repro-repo-nextjs-hls-bug

To Reproduce

  1. npm run dev
  2. Go to /test-pages
  3. It shows HLS export is OK
  4. Go to /test-app
  5. It shows HLS export is undefined

Code in both routes exactly same.

btw swcMinify: false doesn't help.

Except non-helping swcMinify: false, the issue is very similar to #43292

Current vs. Expected behavior

Current:
default export of hls.js is broken

Expected:
default export to return hls.js export

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
Binaries:
  Node: 19.0.1
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: 7.16.0
Relevant Packages:
  next: 14.0.2-canary.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A

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

App Router

Additional context

Tested in 13.5.6 and 14+ versions.
@maybephilipp maybephilipp added the bug Issue was opened via the bug report template. label Oct 31, 2023
@nextjs-bot
Copy link
Collaborator

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

@nextjs-bot nextjs-bot added the stale The issue has not seen recent activity. label Apr 28, 2025
@nextjs-bot
Copy link
Collaborator

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!

@nextjs-bot nextjs-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issue was opened via the bug report template. stale The issue has not seen recent activity.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@maybephilipp @nextjs-bot