Error when using arkenv in client-side bundle

[Robot-Inventor]

Starting with arkenv 0.9.0, an error occurs during build when trying to use arkenv in a Next.js client bundle. It seems that arkenv imports node:module, which causes errors when building the client bundle.

By default, Next.js does not allow environment variables to be referenced from the client bundle, but you can reference them by adding the NEXT_PUBLIC_ prefix, so in my project I was using code similar to the following:

const parsedEnv = arkenv(ClientEnvSchema, {
    env: {
        NEXT_PUBLIC_SITE_URL: process.env.NEXT_PUBLIC_SITE_URL
    }
});

Is this a bug or intended behavior? If it is an intended behavior, are there any plans to make arkenv available in client bundles again? (Apologies if this was intended and was planned to be implemented in #655)

[yamcodes]

Hey @Robot-Inventor! Thanks for reporting this, and sorry about the trouble!

This is indeed a regression from v0.9.0 - an internal top-level import { createRequire } from "node:module" in the core package breaks client-side bundling since Webpack (what Next.js uses) tries to resolve it at build time.

ArkEnv is meant to work across runtimes and environments, so this is a bug. That said, there's no official Next.js plugin yet (tracked in #655 like you mentioned) and no examples/tests for it, so there may be other rough edges too.

Your report is really helpful for understanding real-world usage - I'll take it into account for #655. I'll also look into making that node:module import not break non-Node bundling contexts. No ETA, but it's on my radar!

[yamcodes]

Should be fixed in v0.10.0 - we are no longer importing node:module. Feel free to reopen if this issue persists, though. Give it a shot!