Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

About

An example on how to migrate a CLI-generated project from Atomic v2 to Atomic v3

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Atomic

This project was generated with @coveo/create-atomic.

Setup environment

The root folder should contain a .env file. Replace all placeholder variables (<...>) by the proper information for your organization. Consult the example configuration file named .env.example as needed. For more involved configurations, you can modify the request parameters used in the lambda/functions/token/token.ts file.

CDN

By default, the project installs the latest major Atomic version, v2, to allow types and more advanced customizations. Coveo Headless is also installed with Atomic and accessible at @coveo/headless.

When running, the app will use the bundled Atomic, but using the CDN is a viable option, just make sure you're using the same minor version of Atomic as the one bundled. It could cause issues with your custom components if the minor version differs. E.g., if you have @coveo/atomic@2.0.0 installed, use the following CDN link at path https://static.cloud.coveo.com/atomic/v2.0/.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.

npm run build

Builds the Stencil project for production.

npm run deploy

Builds the app for production and manually deploys the search page using the Coveo CLI deploy command.

Learn More

To learn more about Atomic, check out the Atomic documentation.

About

An example on how to migrate a CLI-generated project from Atomic v2 to Atomic v3

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages