Published in
1 min readAug 12, 2018
Making Angular AMP friendly?
Didn’t have the time to dig in so here’s a few thoughts just based on the initial errors that popped up.
I’m guessing they’re linked to the assumption that you’ll still want to client side render the page in JavaScript, which is not a good assumption with AMP.
- Component tags need to be either eliminated or re-named following Server side rendering.
- You would probably pull out the platform browser and server transition (not sure if this works already, may be interesting to test)
- You would need to prevent the injected script tags / files from getting inserted
This might not be super complicated for someone with a few people who can dig in, but I haven’t seen it documented anywhere just yet.