rsnext/examples/using-preact
Luc Leray f52955ec94
Clean up examples package.json (#27121)
Clean up package.json files in the `examples` directory:
- Add `private: true`
- Remove `version` (because they are irrelevant for packages that are not meant to be published)
- Remove `name` (because they are optional for packages that are not meant to be published, and when someone clones an example, they often rename it and the property becomes stale)
- Remove `author`
- Remove `description`
- Remove `license`

Also remove `with-dynamic-app-layout` example completely, since it does the same as `layout-component` (https://github.com/vercel/next.js/pull/27121#discussion_r668178408).

## Documentation / Examples

- [x] Make sure the linting passes
2021-07-12 19:58:03 +00:00
..
pages Update using-preact example's dependencies (#18493) 2020-10-29 22:52:27 +00:00
.gitignore Added .gitignore to examples that are deployed to vercel (#15127) 2020-07-16 10:52:23 -04:00
next.config.js feat(examples): use next-plugin-preact on using-preact example (#18588) 2020-11-05 16:56:58 +00:00
package.json Clean up examples package.json (#27121) 2021-07-12 19:58:03 +00:00
README.md docs: add 'Open in StackBlitz' buttons to various examples (#25853) 2021-06-08 20:45:02 +00:00

Preact example

This example uses Preact instead of React. It's a React like UI framework which is fast and small.

Preview

Preview the example live on StackBlitz:

Open in StackBlitz

How to use

Execute create-next-app with npm or Yarn to bootstrap the example:

npx create-next-app --example using-preact using-preact-app
# or
yarn create next-app --example using-preact using-preact-app

Deploy it to the cloud with Vercel (Documentation).

Aliasing react -> preact

Using preact with next.js depends on aliasing react packages to preact ones (like @preact/compat). This is done directly in the package.json dependencies.

next-plugin-preact

This example was updated to use next-plugin-preact and now requires minimal configuration, if you want to add preact without a plugin, or see how it works, head to the previous next.config.js.