RelativeTime component appears broken

[pveierland]

Description

The typing and import of RelativeTime component appears broken in v36.27.

Steps to reproduce

1. Create App.tsx with:

import { RelativeTime } from "@primer/react";

export default function App() {
  return (
    <RelativeTime date={new Date("2020-01-01T00:00:00Z")} noTitle={true} />
  );
}

2. When compiling locally with 36.27.0, this results in the type error Type 'Date' is not assignable to type 'never'.

CodeSandbox 36.27.0 Error: Could not find module in path: '@primer/react/lib/node_modules/@oddbird/popover-polyfill/dist/popover-fn.js' relative to '/node_modules/@primer/react/lib/TooltipV2/Tooltip.js'

CodeSandbox 35.10.0: Error: Module '"@primer/react"' has no exported member 'RelativeTime'.

Version

v36.27

Browser

Chrome, Firefox

[Raj3110]

Code runs perfectly fine!! despite of having type errors.

[github-actions]

Uh oh! @Raj3110, the image you shared is missing helpful alt text. Check #4836 (comment).

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.

🤖 Beep boop! This comment was added automatically by github/accessibility-alt-text-bot.

[lesliecdubs]

Hi, thanks for reporting. Are you able to share more about the environment where you're running into this? Are you using a framework like Next.js?

[0xtrou]

while building our nextjs app, I got error

unhandledRejection Error: Cannot find module '../node_modules/@oddbird/popover-polyfill/dist/popover-fn.js'

[pveierland]

Hi, thanks for reporting. Are you able to share more about the environment where you're running into this? Are you using a framework like Next.js?

Yes, using @next==14.2.5 and typescript==5.5.4 locally.

[lesliecdubs]

Hi, thanks for letting us know. We think this likely has to do with the popover polyfill mentioned in #4836 (comment). Another instance of this bug here: #4280 (comment).

@keithamus do you know of any workarounds for folks using Primer who run into this?