Conversation
| - [default] - Default template with all features. | ||
|
|
||
| ### Using Yarn | ||
| - [material] - material-ui template using preact-material-components |
There was a problem hiding this comment.
"material template...." material-ui might be confusing with react's material-ui
lukeed
left a comment
lukeed
left a comment
There was a problem hiding this comment.
Have to step out, but started going thru this.
| ### Templates | ||
| Note: | ||
|
|
||
| 1. You can run dev server using`HTTPS` then you can use the following `HTTPS=true preact watch` |
| --src Entry file (index.js) [string] [default: "src"] | ||
| --port, -p Port to start a server on [string] [default: "8080"] | ||
| --host, Hostname to start a server on [string] [default: "0.0.0.0"] | ||
| --https Use HTTPS? [boolean] [default: false] |
| ### Installation | ||
|
|
||
| ### Commands | ||
| Prerequisites: [Node.js](https://nodejs.org/en/) required version (> 6.x) |
There was a problem hiding this comment.
How about > **Important:** Node v6.x is the minimum requirement.
|
Made a few tweaks and put it into gist: I've bullet pointed my suggested updates into a review |
silverlight513
left a comment
silverlight513
left a comment
There was a problem hiding this comment.
Updates
- Moved the templates subsection to under the Official Templates section
- Changed title from
templatetoCustom templates - Updated content of
Custom templates
|
@silverlight513 Thanks! 🙏 I think this is a good example to point out that we need to clarify that the "template" in Nesting them under each other will surely, imo, add to the confusion. |
|
Ah, from the looks of it they appeared to be the same thing. My bad. @lukeed, would you mind explaining the difference between the |
|
@lukeed @silverlight513 thanks for the reviews and your time 🙏 Official Templates Till now (the current version) we were just using the code in the examples folder for boot-strapping new projects using preact cli. But in the next version (v2.0) we moved to custom-templates which will pull the the project from the The contents in the Template flag The template here refers to a custom By default in preact-cli we don't expose the HTML file as CRA does. So, we support a You can use them in the following way:
|
|
@silverlight513 No problem, I'm sure you're not/won't be the only one. The The "Official Templates" (or any template) is a new 2.0 feature which allows you to scaffold a new project from an external repository. Here, "template" is synonymous with "boilerplate." The motivation here is to allow community-driven, reusable templates so that users don't feel restricted to what's included in Preact CLI directly. |
|
We'll definitely update this as we go along. Better to have something reflective of the current repo sooner rather than later. |
* master: (166 commits) Use `publicPath` for SW & Manifest paths (#323) Purge `examples` dir (#393) Update Readme (#383) Add `preact list` command (#384) linters are dumb inject / replace strings in extracted contents adding flag to disable service worker Convert `css-loader` options to an Object (#349) remove `offline-plugin` (unused) remove `mkdirp` (unused) remove `less` dependencies fix linter move `htmlPlugin` to `render-html-plugin.js` install `css|postcss|style-loader` & regen `yarn.lock` remove `chunk.modules` deprecation notice rewrite server’s `webpack.config` without blocks rewrite client’s `webpack.config` without blocks install `webpack-merge` rewrite base `webpack.config` w/o blocks light refactor ... # Conflicts: # src/lib/webpack/webpack-base-config.js
4 participants
Updates the
READMEreflecting changes tocustom templateswhich is the highlight for 2.0.Any inputs are more than welcome.
Please do not merge this PR until we are planning for a release.