diff --git a/docs/components/functional-components.md b/docs/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/docs/components/functional-components.md
+++ b/docs/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v2/components/functional-components.md b/versioned_docs/version-v2/components/functional-components.md
index 609829f2e..35d20d7b5 100644
--- a/versioned_docs/version-v2/components/functional-components.md
+++ b/versioned_docs/version-v2/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v3/components/functional-components.md b/versioned_docs/version-v3/components/functional-components.md
index 609829f2e..35d20d7b5 100644
--- a/versioned_docs/version-v3/components/functional-components.md
+++ b/versioned_docs/version-v3/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.0/components/functional-components.md b/versioned_docs/version-v4.0/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.0/components/functional-components.md
+++ b/versioned_docs/version-v4.0/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.1/components/functional-components.md b/versioned_docs/version-v4.1/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.1/components/functional-components.md
+++ b/versioned_docs/version-v4.1/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.2/components/functional-components.md b/versioned_docs/version-v4.2/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.2/components/functional-components.md
+++ b/versioned_docs/version-v4.2/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.3/components/functional-components.md b/versioned_docs/version-v4.3/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.3/components/functional-components.md
+++ b/versioned_docs/version-v4.3/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.4/components/functional-components.md b/versioned_docs/version-v4.4/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.4/components/functional-components.md
+++ b/versioned_docs/version-v4.4/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.5/components/functional-components.md b/versioned_docs/version-v4.5/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.5/components/functional-components.md
+++ b/versioned_docs/version-v4.5/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.6/components/functional-components.md b/versioned_docs/version-v4.6/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.6/components/functional-components.md
+++ b/versioned_docs/version-v4.6/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.7/components/functional-components.md b/versioned_docs/version-v4.7/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.7/components/functional-components.md
+++ b/versioned_docs/version-v4.7/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.8/components/functional-components.md b/versioned_docs/version-v4.8/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.8/components/functional-components.md
+++ b/versioned_docs/version-v4.8/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file
diff --git a/versioned_docs/version-v4.9/components/functional-components.md b/versioned_docs/version-v4.9/components/functional-components.md
index 91c7d4536..cd3b27af2 100644
--- a/versioned_docs/version-v4.9/components/functional-components.md
+++ b/versioned_docs/version-v4.9/components/functional-components.md
@@ -102,3 +102,7 @@ There are a few major differences between functional components and class compon
 * are stateless.
 
 When deciding whether to use functional components, one concept to keep in mind is that often the UI of your application can be a function of its state, i. e., given the same state, it always renders the same UI. If a component has to hold state, deal with events, etc, it should probably be a class component. If a component's purpose is to simply encapsulate some markup so it can be reused across your app, it can probably be a functional component (especially if you're using a component library and thus don't need to style it).
+
+:::caution
+Stencil does not support re-exporting a functional component from a "barrel file" and dynamically rendering it in another component. This is a [known limitation](https://github.com/ionic-team/stencil/issues/5246) within Stencil. Instead, either use class components and remove the import or import the functional component directly.
+:::
\ No newline at end of file