Skip to content

Commit 20308ba

Browse files
author
Arthur Evans
committed
Merge commit '60890d4' into build-for-production
2 parents 20df04e + 60890d4 commit 20308ba

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/_guide/build.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The [prpl-server](https://github.com/Polymer/prpl-server) project is a Node.js w
277277

278278
This section describes the requirements for building applications using LitElement. Use this section if you're creating your own build setup.
279279

280-
LitElement is packaged as a set of ES modules, written in modern JavaScript (ES 2017). These are supported natively in modern browsers (Chrome, Safari, Firefox, and soon Edge, for example). LitElement also uses bare module specifiers, which are not supported by any browsers yet.
280+
LitElement is packaged as a set of ES modules, written in modern JavaScript (ES 2017). These are supported natively in modern browsers (Chrome, Safari, Firefox, and Edge, for example). LitElement also uses bare module specifiers, which are not supported by any browsers yet.
281281

282282
When building an app using LitElement, your build system will need to handle the following:
283283

@@ -298,7 +298,7 @@ LitElement uses bare module specifiers to import modules from the lit-html libra
298298
import {html} from 'lit-html';
299299
```
300300

301-
This syntax isn't supported by any browsers at present, so the build system needs to handle them: either by transforming the specifier to one that works for ES modules in the browser, or by producing a different type of module as output.
301+
Browsers currently only support loading modules from URLs or relative paths, not bare names referring to e.g. an npm package, so the build system needs to handle them: either by transforming the specifier to one that works for ES modules in the browser, or by producing a different type of module as output.
302302

303303
Webpack automatically handles bare module specifiers; for Rollup, you'll need a plugin ([@rollup/plugin-node-resolve](https://github.com/rollup/plugins/tree/master/packages/node-resolve)).
304304

0 commit comments

Comments
 (0)