f52955ec94
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 |
||
|---|---|---|
| .. | ||
| pages | ||
| .babelrc | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
Example app with babel-macros
This example features how to configure and use babel-macros which allows you to easily add babel plugins which export themselves as a macro without needing to configure them.
Preview
Preview the example live on StackBlitz:
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app with npm or Yarn to bootstrap the example:
npx create-next-app --example with-babel-macros with-babel-macros-app
# or
yarn create next-app --example with-babel-macros with-babel-macros-app
Deploy it to the cloud with Vercel (Documentation).
Note
You'll notice the configuration in .babelrc includes the babel-macros
plugin, then we can use the preval.macro in pages/index.js to pre-evaluate
code at build-time. preval.macro is effectively transforming our code, but
we didn't have to configure it to make that happen!
Specifically what we're doing is we're prevaling the username of the user who ran the build.