Skip to content
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.

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

regression introduced between 13.4.13 - 13.4.15 - appdir + custom server = assetPath issue #61383

Closed
morriq opened this issue Jan 30, 2024 · 1 comment · Fixed by #61676
Closed
Labels
bug Issue was opened via the bug report template. locked

Comments

@morriq
Copy link

morriq commented Jan 30, 2024

Link to the code that reproduces this issue

https://github.com/morriq/next-cdn-issue/

To Reproduce

  1. clone repository https://github.com/morriq/next-cdn-issue/
  2. go to ./apps/app-dir-custom-server
  3. pnpm i && pnpm build && pnpm start
  4. in browser you should see some assets loaded, some not

Current vs. Expected behavior

based on reproduction I expect all assets are not loaded. assets are served on different server.

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.6.7
Relevant Packages:
  next: 14.1.0
  eslint-config-next: N/A
  react: 18.0.0
  react-dom: 18.0.0
  typescript: N/A
Next.js Config:
  output: N/A

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

App Router

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

next start (local), Other (Deployed)

Additional context

related issue #51223

@morriq morriq added the bug Issue was opened via the bug report template. label Jan 30, 2024
@ijjk ijjk closed this as completed in 19c2e19 Feb 5, 2024
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. locked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant