rsnext/examples/with-patternfly
2022-05-27 21:21:40 +00:00
..
pages Fix PatternFly 4 example (#25356) 2021-05-22 15:06:14 +00:00
.gitignore Added .gitignore to examples that are deployed to vercel (#15127) 2020-07-16 10:52:23 -04:00
next.config.js fix(examples): future.webpack5 -> top level webpack5 (#26175) 2021-06-16 12:07:15 +00:00
package.json Update next-transpile-modules to 9.0.0 across examples (#30418) 2021-10-27 09:48:28 +00:00
README.md Update pnpm create next-app for latest pnpm 6 and 7 (#37254) 2022-05-27 21:21:40 +00:00

PatternFly 4 example

This example shows how to use Next.js with the PatternFly 4 design system.

Deploy your own

Deploy the example using Vercel or preview live with StackBlitz

Deploy with Vercel

How to use

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

npx create-next-app --example with-patternfly with-patternfly-app
# or
yarn create next-app --example with-patternfly with-patternfly-app
# or
pnpm create next-app --example with-patternfly with-patternfly-app

Deploy it to the cloud with Vercel (Documentation).

Troubleshooting

Global CSS cannot be imported from within node_modules

PatternFly 4 packages published on npm use Global CSS imports for styling of React components, which is not supported by Next.js. To workaround this issue, this example uses next-transpile-modules to transpile the packages during compilation. As a consequence, all packages that depend on @patternfly/react-styles need to be transpiled as well.

If you receive this error, verify whether all packages that depend on @patternfly/react-styles are specified in next.config.js.

PatternFly components do not appear to be styled

If your Next.js application compiles successfully, but PatternFly components in your application do not appear to be styled, make sure you have applied the global PatternFly stylesheet in pages/_app.js:

// In pages/_app.js
import App from 'next/app'
import '@patternfly/react-core/dist/styles/base.css'

...

All components styles are imported when using a PatternFly component

This is expected behavior in development mode. Tree shaking will remove these imports in production builds.