Links from non-AMP pages to AMP pages causes broken pages

[kevva]

Bug report

Describe the bug

When going from a regular page with amp: false to a page that has amp: true set, it won't render the AMP page correctly. E.g. all <amp-img> tags won't be visible and other AMP components won't work either.

Worth noting is that this doesn't happen during development.

To Reproduce

Clone https://github.com/kevva/next-link-amp and do the following:

1. Run npm run build
2. Run npm run start
3. Go to the "Amp" link and the image that should be there won't be visible
4. Go to "Amp (without Link)" and the image will show

[ijjk]

Hi, it looks like the provided repo to reproduce is 404ing. I don't seem to be able to reproduce this locally on a minimal Next.js app using the latest version of Next.js v9.3.3

[kevva]

I'm sorry, I hadn't made it public.

[ijjk]

Hi, thanks for providing the reproduction. It looks like this is due to not exporting the config in the same line e.g. export const config = {...}. I opened a PR to fix the mismatching behavior between production and development which should resolve this.

[kevva]

Oh, interesting, nice find.

[kevva]

@ijjk, I guess this might be out of scope since it's an experimental feature, but when setting modern: true it breaks in the same way as well. Probably because the pages are named [page].module.js instead of [page].js.

[ijjk]

@kevva right, I opened a follow-up PR to handle the new modern experimental feature here

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.