Bare `process` import breaks Deno compatibility
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- eslint, node.js, typescript
- Domain
- api
Research direction
Start with src/configuration.ts:4 and reproduce the import failure using the Deno command and test.ts setup described in the issue. Check the existing ESLint configuration for where the unicorn/prefer-node-protocol rule belongs. Done means the SDK imports without the reported Deno error and linting prevents bare Node.js built-in imports.
Written by the indexing model from the issue text.
Description
Description
The SDK crashes when imported in Deno due to a bare process specifier in src/configuration.ts:4:
import { arch, platform, version as nodeVersion } from 'process';
Deno requires the node: prefix for Node.js built-in modules. This causes a fatal SyntaxError:
error: Uncaught SyntaxError: The requested module 'process' does not provide an export named 'arch'
Steps to reproduce
- Install Deno
- Create a test file:
import Zitadel from "./dist/index.js";
const client = Zitadel.withAccessToken("https://example.zitadel.cloud", "fake-token");
- Run:
deno run --allow-read --allow-env --allow-net --allow-sys test.ts
Expected behavior
The SDK should import and work without errors in Deno.
Proposed fix
- Change
from 'process'tofrom 'node:process'insrc/configuration.ts - Add
eslint-plugin-unicornwith theunicorn/prefer-node-protocolrule to prevent regressions
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from zitadel/zitadel-node
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
zitadel/zitadel-node#138 ·
-
Release SDK for V5 Open
zitadel/zitadel-node#97 · 1 comment · 4 reactions · 1 assignee ·
All issues in zitadel/zitadel-node
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100