Warning instead of error for 'new Date()' under dynamicIO

[filipjnc]

Since [email protected] the build throws if it encounters routes with 'new Date()'. I read the docs and I generally agree reading time is ambiguous. But I also find the ergonomics of the reactive use case quite bad. Having to use useState + useEffect to just achieve a 'new Date()' feels convoluted.

Is this supposed to be the final solution or is the team working to improve the DX of the reactive use case? Cause if so, I'd suggest to keep it a warning during build.

[icyJoseph]

I think, you can wrap the call to new Date in use cache, and that is like, the way to make the IO-ness of it, sort of go away:

async function getNewDate() {
  'use cache'

  return new Date();
}


export default async function Home() {
  const date = await getNewDate();
  return (
    <pre>{date.toISOString()}</pre>
  );
}