From 3934f0a8332df5c0f22ce0b3f419a618ec11eee0 Mon Sep 17 00:00:00 2001 From: santoshyadavdev Date: Mon, 14 Sep 2020 15:12:23 +0530 Subject: [PATCH] docs(elements): convert the `ng add` command to code-example (#38834) the command was hardly visible currently changing it to shell for visibility PR Close #38834 --- aio/content/guide/elements.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/aio/content/guide/elements.md b/aio/content/guide/elements.md index 7e84417df2..28a2751f9d 100644 --- a/aio/content/guide/elements.md +++ b/aio/content/guide/elements.md @@ -119,7 +119,14 @@ The recently-developed [custom elements](https://developer.mozilla.org/en-US/doc In browsers that support Custom Elements natively, the specification requires developers use ES2015 classes to define Custom Elements - developers can opt-in to this by setting the `target: "es2015"` property in their project's [TypeScript configuration file](/guide/typescript-configuration). As Custom Element and ES2015 support may not be available in all browsers, developers can instead choose to use a polyfill to support older browsers and ES5 code. -Use the [Angular CLI](cli) to automatically set up your project with the correct polyfill: `ng add @angular/elements --project=*your_project_name*`. +Use the [Angular CLI](cli) to automatically set up your project with the correct polyfill: + + + +ng add @angular/elements --project=*your_project_name* + + + - For more information about polyfills, see [polyfill documentation](https://www.webcomponents.org/polyfills). - For more information about Angular browser support, see [Browser Support](guide/browser-support).