[x] Build (npm run build) was run locally for affected output targets
[x] Tests (npm test) were run locally and passed
[x] Prettier (npm run prettier) was run locally and passed
Pull request type
Please check the type of change your PR introduces:
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
What is the current behavior?
Currently if a user provides a hydrateModule option, the output target creates server side renderable components for all components. If a user wants to slowly roll out SSR as a feature, they won't be able to without manually updating the compiled files.
What is the new behavior?
This patch introduces a new option called excludeServerSideRenderingFor which allows user to provide a list of component tags which should be excluded from being server side rendered.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build) was run locally for affected output targetsnpm test) were run locally and passednpm run prettier) was run locally and passedPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Currently if a user provides a
hydrateModuleoption, the output target creates server side renderable components for all components. If a user wants to slowly roll out SSR as a feature, they won't be able to without manually updating the compiled files.What is the new behavior?
This patch introduces a new option called
excludeServerSideRenderingForwhich allows user to provide a list of component tags which should be excluded from being server side rendered.Does this introduce a breaking change?
Other information
n/a