https://github.com/atomicojs/example-next-js
https://github.com/atomicojs/example-next-js
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/atomicojs/example-next-js
- Owner: atomicojs
- Created: 2022-07-08T15:21:55.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2022-07-08T16:01:20.000Z (almost 4 years ago)
- Last Synced: 2025-04-30T00:35:11.743Z (about 1 year ago)
- Language: JavaScript
- Homepage: example-next-js-mocha.vercel.app
- Size: 72.3 KB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## How is it possible that Atomico supports Next.js SSR?
[](https://twitter.com/atomicojs)
[](https://discord.gg/7z3rNhmkNE)
[](https://atomico.gitbook.io/doc/)
[](https://webcomponents.dev/create/atomico)
Atomico uses webcomponents, but it is agnostic to the rendering system, thanks to the [@atomico/react](https://github.com/atomicojs/react) package, atomico is able to extend its use support to any platform that works with React, example Next.js.
> This example is introductory, to exemplify the use of @atomico/react manually, there is a second package @atomico/exprots that does all this automatically by distributing your component created with Atomico as a package 😉.
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
## what is different about Next.js to support Atomico webcomponents with SSR?
**1. [pages/\_app.jsx](./pages/_app.jsx)**
```jsx
import "@atomico/react/proxy";
import "../styles/globals.css";
function MyApp({ Component, pageProps }) {
return ;
}
export default MyApp;
```
**2. [pages/index.jsx](./pages/index.jsx)**: here the magic happens.
## Getting Started
First, run the development server:
```bash
npm run dev
# or
yarn dev
```
Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
You can start editing the page by modifying `pages/index.js`. The page auto-updates as you edit the file.
[API routes](https://nextjs.org/docs/api-routes/introduction) can be accessed on [http://localhost:3000/api/hello](http://localhost:3000/api/hello). This endpoint can be edited in `pages/api/hello.js`.
The `pages/api` directory is mapped to `/api/*`. Files in this directory are treated as [API routes](https://nextjs.org/docs/api-routes/introduction) instead of React pages.
## Learn More
To learn more about Next.js, take a look at the following resources:
- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!
## Deploy on Vercel
The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.