Migrate from unbuild to obuild

[vicb]

unenv now uses obuild (see unjs/unenv#504)

This PR migrates the cf preset to use obuild

/cc @pi0

Some file are missing type exports, i.e. tls is missing:

export declare const checkServerIdentity: typeof import("tls").checkServerIdentity,
	connect: typeof import("tls").connect,
	createSecureContext: typeof import("tls").createSecureContext,
	convertALPNProtocols: any,
	SecureContext: any,
	TLSSocket: typeof import("tls").TLSSocket;

Pooya's comment:

Dts generation issue might come from the new isolated decl generator (we need more explicit exports)
But if is a bug we can also check with kevin (dts plugin maintainer)

I'll investigate This is indeed related to isolated declaration. Should be fine as this is already the way unenv is since it migrated to obuild.

Todo

• Blocked on Switch to tinyglobby to support Node < 22 unjs/obuild#21
• Check the d.ts generation

---

• Tests
  • TODO (before merge)
  • Tests included
  • Tests not necessary because: covered by existing tests
• Wrangler / Vite E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required
  • Not required because:
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Documentation not necessary because: no user facing change
• Wrangler V3 Backport
  • TODO (before merge)
  • Wrangler PR:
  • Not necessary because: not a wrangler change

[changeset-bot]

🦋 Changeset detected

Latest commit: 4cdce3a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@cloudflare/unenv-preset	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@9243

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@9243

miniflare

npm i https://pkg.pr.new/miniflare@9243

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@9243

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@9243

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@9243

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@9243

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@9243

wrangler

npm i https://pkg.pr.new/wrangler@9243

commit: 4cdce3a

[petebacondarwin]

LGTM - out of interest, why are we updating to this experimental tool?

[vicb]

LGTM - out of interest, why are we updating to this experimental tool?

unbuild is being replaced by obuild so probably needed at some point.
and it's what unenv uses now (see PR description for ref)

[vicb]

This breaks windows CI:

.\dist\runtime\polyfill\performance.mjs
file:///D:/a/workers-sdk/workers-sdk/node_modules/.pnpm/[email protected]/node_modules/rolldown/dist/shared/src-PO2pehsE.mjs:2247
	const wrapper = new Error(summary);
	                ^

Error: Build failed with 1 error:

[PARSE_ERROR] Error: Invalid escape sequence
   ╭─[ #entry:1:61 ]
   │
 1 │ import * as _lib from "D:\a\workers-sdk\workers-sdk\packages\unenv-preset\dist\index.mjs";
   │                                                             ─┬  
   │                                                              ╰── 
───╯

FYI @pi0

We will revert and investigate

[petebacondarwin]

This is a classic case of injecting paths into code as a string. There is probably something that looks like:

const code = `import * as _lib from "${filePath}";`;

which works fine on Unix but with Windows paths the \ characters become escape sequences.

Instead you need something like:

const code = `import * as _lib from ${JSON.stringify(filePath)};`;