Request: publish a release with the Windows entry-path fix (#12)

Open
  • Is something wrong?
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js, typescript
Domain
release

Research direction

Check the npm version of @rendiv/bundler against the master commits 905d2b7 and 39433db, which the issue says fix the Windows entry-path problem. The requested outcome is a published release containing #12; the payload does not name a release workflow or test to run.

Written by the indexing model from the issue text.

Description

Thanks for fixing #11 in #12. The fix is on master (905d2b7 "fix: normalize and escape render entry import paths" and 39433db "fix: preserve literal backslashes in POSIX entry paths"), but the latest npm release is still 0.2.6 (2026-06-07), so @rendiv/bundler from npm still fails on Windows.

Repro with @rendiv/[email protected] on Windows 11, Node 24:

import path from 'node:path';
import { bundle } from '@rendiv/bundler';

await bundle({ entryPoint: path.resolve('src/index.tsx') }); // e.g. C:\Users\me\video\src\index.tsx

Rollup failed to resolve import "C:Usersmevideosrcindex.tsx" from ".../__rendiv_entry__.jsx"

Built from master, the same call works. Could you publish a release that includes #12 when you get a chance? In the meantime, passing the entry point with forward slashes (entryPoint.replace(/\\/g, '/')) works around it.

Dominant language
TypeScript
Stars
159
Forks
32
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from thecodacus/rendiv

All issues in thecodacus/rendiv

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.