Atoms are not working in browser (non-node.js, non-next.js) environment

[akaynarov]

Issue Summary

Atoms are not working in non-next.js context. The Credits and

Steps to Reproduce

1. Make a normal non-next.js project.
2. Import the CalProvider
3. The app crashes with Uncaught ReferenceError: process is not defined.

The error is because process is only accessible in node.js environements and not present in browser environments.

The documentation states that the library should work both in Next.js and React.js

Actual Results

• The app is crashing with: Uncaught ReferenceError: process is not defined

Expected Results

• Atoms are working in browser environment.

Technical details

• React version: 19.1.2
• "@calcom/atoms": "^1.1.1"

Evidence

Point of issue in the library:

• Tested by importing @calcom/atoms and using the provider.

Error in the compiled code:

The issue is from the Icon component.

[linear]

CAL-6131 Atoms are not working in pure React.js environment.

[chintanparikh]

Any plans to address this? This is blocking us from using cal.com

[akaynarov]

@hemantmm When do you plan to release this?

[jo-rs]

This is also blocking us from using cal.com for our platform. We are paying for the platform subscription, but we'll need to cancel and find a different solution if this is not addressed as it's critical.

[hemantmm]

@hemantmm When do you plan to release this?

Yet to be reviewed by the maintainer.

[chintanparikh]

@anikdhabal can you help us get this routed appropriately?

[JacobNWolf]

Also encountering this issue.

[manpreetssethi]

Any chance this can be fixed soon? Noticed there's a PR waiting to be reviewed/merged.

@Ryukemeister

[SafaElmali]

This isn’t a medium priority. It’s definitely high priority. We’re unable to use atoms, which is forcing us to move to an alternative solution.