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.

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

Support assetPrefix for Link component ? #5899

Closed
revskill10 opened this issue Dec 16, 2018 · 3 comments
Closed

Support assetPrefix for Link component ? #5899

revskill10 opened this issue Dec 16, 2018 · 3 comments

Comments

@revskill10
Copy link
Contributor

revskill10 commented Dec 16, 2018 •
edited

Feature request

Support assetPrefix with next/link component.

Describe the solution you'd like

Provide assetPrefix props for next/link component.

Additional context

This feature is needed in case we have multiple NextJS apps on the same domain with different assetPrefix .
Note that, even page urls are on the same domain, assetPrefix might be on different CDN host.
@timneutkens
Copy link
Member

Duplicate of #4998

@timneutkens timneutkens marked this as a duplicate of #4998 Dec 31, 2018
@revskill10
Copy link
Contributor Author

revskill10 commented Jan 27, 2019 •
edited

#4998 doesn't solve my issue.
In my case, each assetPrefix is a full CDN domain , like https://cdn-1.cdn.com/project1 . The Link component has no knowledge about the domain of NextJS application is being served.

@timneutkens
Copy link
Member

@revskill10 I'm sure you mean the same problem / feature though. If not please write up a more detailed issue about what you're trying to solve, because it sounds like you want the exact same solution, being able to link to a specific subpath.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@revskill10 @timneutkens