Files
web/apps/scandic-web
Anton Gunnarsson cbf9e7b7c2 Merged in chore/next15 (pull request #1999)
chore (SW-834): Upgrade to Next 15

* wip: apply codemod and upgrade swc plugin

* wip: design-system to react 19, fix issues from async (search)params

* wip: fix remaining issues from codemod

serverClient is now async because context use headers()
getLang is now async because it uses headers()

* Minor cleanup

* Inline react-material-symbols package

Package is seemingly not maintained any more and doesn't support
React 19. This copies the package source into `design-system`,
makes the necessary changes for 19 and export it for others to use.

* Fix missing awaits

* Disable modal exit animations

Enabling modal exit animations via isExiting prop is causing
modals to be rendered in "hidden" state and never unmount.
Seems to be an issue with react-aria-components,
see https://github.com/adobe/react-spectrum/issues/7563.
Can probably be fixed by rewriting to a solution similar to
https://react-spectrum.adobe.com/react-aria/examples/framer-modal-sheet.html

* Remove unstable cache implementation and use in memory cache locally

* Fix ref type in SelectFilter

* Use cloneElement to add key prop to element


Approved-by: Linus Flood
2025-06-02 11:11:50 +00:00
..
2025-04-28 12:40:52 +00:00
2025-05-22 14:00:38 +02:00
2025-04-23 22:40:46 +00:00
2025-04-23 22:40:46 +00:00
2025-04-07 12:17:35 +02:00

This is a Next.js project bootstrapped with create-next-app.

Getting Started

  • Firt, make sure you have built the design-system once:
yarn workspace @scandic-hotels/design-system build
  • Create a .env.local file in the root of the scandic-web directory with the keys from the .env.example file.

  • Then run the development server:

yarn dev

Open http://localhost:3000 with your browser to see the result.

Caching

You have the choice to either use redis (via redis-api; a tiny http proxy) or in-memory/unstable_cache (depending on edge or node). Setting REDIS_API_HOST will configure it to use the distributed cache, not providing it will fall back to in-memory/unstable_cache When pointing to the azure hosted variant you also need to provide REDIS_API_KEY

Locally it's easiest is to spin everything up using docker/podman - podman compose up or docker-compose up This will also spin up Redis Insight so that you can debug the cache.

  • Navigate to http://localhost:5540
  • Click 'Add Redis database'
  • Provide Connection URL redis://redis:6379

Icons / Material Symbols

Read the README.md in the monorepo root.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!