Skip to content

Mention running the command on home page#536

Merged
bebraw merged 1 commit into
webpack:masterfrom
Flimm:index-command-line-example
Jan 6, 2017
Merged

Mention running the command on home page#536
bebraw merged 1 commit into
webpack:masterfrom
Flimm:index-command-line-example

Conversation

@Flimm
Copy link
Copy Markdown
Contributor

@Flimm Flimm commented Dec 21, 2016

Add one sentence to the home page, to make it clear that you need to run a webpack command to actually build the thing.

@jsf-clabot
Copy link
Copy Markdown

jsf-clabot commented Dec 21, 2016

CLA assistant check
All committers have signed the CLA.

Copy link
Copy Markdown
Member

@TheLarkInn TheLarkInn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a nitpick, I think it feels easier to have them run webpack

Would you kind altering? @bebraw any thoughts?

@bebraw
Copy link
Copy Markdown
Contributor

bebraw commented Dec 22, 2016

I agree with the basic idea that the copy is too abstract. It took a while for me at least to see what's going on. I imagine it's only harder for people not familiar with the idea of bundling.

Adding a sentence like that would help a notch, but it would not remove the underlying issue. If possible, get people not familiar with webpack to take a look at it and see what they think. The copy can be improved based on that feedback.

@bebraw bebraw changed the base branch from develop to master January 1, 2017 13:53
@bebraw
Copy link
Copy Markdown
Contributor

bebraw commented Jan 1, 2017

Can you rebase against master? The development happens against it now (faster deployments).

@bebraw bebraw merged commit 66e5c1d into webpack:master Jan 6, 2017
@bebraw
Copy link
Copy Markdown
Contributor

bebraw commented Jan 6, 2017

Thanks. 👍

@Flimm
Copy link
Copy Markdown
Contributor Author

Flimm commented Jan 6, 2017

Thanks for merging!

bjohansebas added a commit that referenced this pull request May 19, 2026
Webpack 5.107 introduces experiments.html, the html-loader side of
native HTML module support. With the flag on, importing an HTML file
from JavaScript runs its tag references through the webpack pipeline.

What this PR documents:

- The experiments.html flag and its TOC entry.
- The JS-import-HTML usage pattern (no entry-point support yet).
- Inline <style> tags routed through the CSS pipeline as virtual
  exportType: "text" modules, so url() and @import resolve relative to
  the HTML file.
- Inline <script> tags routed through the same entry pipeline as
  <script src>: classic bodies bundle as CommonJS, type="module"
  bodies as ESM, tags rewritten to <script src="...">, auto-upgrade to
  type="module" under output.module.
- <script src> and <link rel="modulepreload"> references becoming real
  webpack entries with shared runtime via dependOn, independent
  modulepreload chunks, and type="module" auto-upgrade.
- webpackIgnore magic comment for HTML (cross-references the existing
  magic comments docs in api/module-methods).

What is explicitly NOT supported in 5.107 (called out in the warning
admonition): HTML entry points (the html-webpack-plugin part). That is
planned for the next minor release. The full story is tracked in
issue #536.

Refs:
- webpack/webpack#20902 (experiments.html flag)
- webpack/webpack#20962 (inline <style>)
- webpack/webpack#20967 (inline <script>)
- webpack/webpack#20949 (<script src> / modulepreload)
- webpack/webpack#20950 (webpackIgnore in HTML)
alexander-akait pushed a commit that referenced this pull request May 19, 2026
…8243)

* docs(experiments): document experiments.html and its HTML behaviors

Webpack 5.107 introduces experiments.html, the html-loader side of
native HTML module support. With the flag on, importing an HTML file
from JavaScript runs its tag references through the webpack pipeline.

What this PR documents:

- The experiments.html flag and its TOC entry.
- The JS-import-HTML usage pattern (no entry-point support yet).
- Inline <style> tags routed through the CSS pipeline as virtual
  exportType: "text" modules, so url() and @import resolve relative to
  the HTML file.
- Inline <script> tags routed through the same entry pipeline as
  <script src>: classic bodies bundle as CommonJS, type="module"
  bodies as ESM, tags rewritten to <script src="...">, auto-upgrade to
  type="module" under output.module.
- <script src> and <link rel="modulepreload"> references becoming real
  webpack entries with shared runtime via dependOn, independent
  modulepreload chunks, and type="module" auto-upgrade.
- webpackIgnore magic comment for HTML (cross-references the existing
  magic comments docs in api/module-methods).

What is explicitly NOT supported in 5.107 (called out in the warning
admonition): HTML entry points (the html-webpack-plugin part). That is
planned for the next minor release. The full story is tracked in
issue #536.

Refs:
- webpack/webpack#20902 (experiments.html flag)
- webpack/webpack#20962 (inline <style>)
- webpack/webpack#20967 (inline <script>)
- webpack/webpack#20949 (<script src> / modulepreload)
- webpack/webpack#20950 (webpackIgnore in HTML)

* docs(magic-comments): document webpackIgnore support in HTML modules

Webpack 5.107 supports the webpackIgnore magic comment inside HTML
modules (when experiments.html is enabled). Placing
<!-- webpackIgnore: true --> before a tag skips URL resolution for its
src/href/srcset attributes, leaving the tag untouched in the emitted
HTML. Adds a new HTML Usage section under the existing webpackIgnore
docs in api/module-methods.

Refs: webpack/webpack#20950
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants