Support `deno.json` and `package.json` without a `name` field
Author: emonadeoCreated Mar 23, 2025Updated Jul 22, 2026
Labelspending triage
Describe the bug
I would love to use vanilla-extract in a Deno environment however currently the getPackageInfo function cannot find a package.json with a name field.
While Deno has compatibility for package.json it would be nice to not have to rely on it.
Reproduction
https://github.com/emonadeo/repro_vanilla-extract_1563
System Info
N/AUsed Package Manager
pnpm
Logs
Couldn't find parent package.json with a name field from '/<redacted>'
Location:
/<redacted>/node_modules/.deno/@[email protected]/node_modules/@vanilla-extract/integration/dist/vanilla-extract-integration.cjs.dev.js:351:11Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- The provided reproduction is a minimal reproducible example of the bug.
Source: vanilla-extract-css/vanilla-extract