4466ba436b
## Description This PR ensures that the default prettier config is used for examples and templates. This config is compatible with `prettier@3` as well (upgrading prettier is bigger change that can be a future PR). ## Changes - Updated `.prettierrc.json` in root with `"trailingComma": "es5"` (will be needed upgrading to prettier@3) - Added `examples/.prettierrc.json` with default config (this will change every example) - Added `packages/create-next-app/templates/.prettierrc.json` with default config (this will change every template) ## Related - Fixes #54402 - Closes #54409 |
||
|---|---|---|
| .. | ||
| 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.
Deploy your own
Deploy the example using Vercel or preview live with StackBlitz
How to use
Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example with-babel-macros with-babel-macros-app
yarn create next-app --example with-babel-macros with-babel-macros-app
pnpm 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.