Repository navigation
fix: resolve framework-specific files when building on Windows - #252
DamianGlowala wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. WalkthroughBoth build configurations now use Suggested reviewers: Merge Risk:
|
There was a problem hiding this comment.
🟢 Approval recommended
There are no active review issues for the cross-platform file-resolution changes.
No open issues 🎉
1 file not reviewed
pnpm-lock.yaml: Generated file
What changed in this PR
This PR updates framework-specific file resolution so Formisch’s core and methods packages can be built on Windows.
Changes:
- Uses
patheto construct paths without assuming Unix-style separators or root paths. - Normalizes resolved module paths before selecting framework-specific files.
- Adds
patheas a development dependency in both packages and updates the lockfile.
| File | Description |
|---|---|
pnpm-lock.yaml |
Records the new pathe dependencies. |
packages/methods/tsdown.config.ts |
Makes framework-specific path construction and resolution cross-platform. |
packages/methods/package.json |
Adds the pathe development dependency. |
packages/core/tsdown.config.ts |
Makes framework-specific path construction and resolution cross-platform. |
packages/core/package.json |
Adds the pathe development dependency. |
Review effort: Balanced
|
Thanks for fixing this! I'd prefer to avoid the extra dependency here. const frameworkFilePath = resolved.id.replace(
/([/\\][\w-]+)\.ts$/,
`$1.${framework}.ts`
);That also keeps rolldown's native ID format. Could you drop |
|
@fabian-hiller should be fine now! :) |
Normalises paths for Windows, so that
@formisch/coreor@formisch/methodscan be built on Windows.Summary by CodeRabbit