v0.1.5
Fixed: spurious errors on Windows
The Windows build could report package-access violations for imports that are perfectly legal — including imports from a file's own directory. Two root causes, both fixed:
- Path canonicalization used
std::fs::canonicalize, which returns\\?\-verbatim paths on Windows; inside those,/isn't treated as a path separator, breaking the rule engine's directory comparisons against resolver-produced paths. Canonicalization now goes throughdunceand yields plainC:\paths. - The internal
node_relativehelper split paths on/only, sopackageDirectoryglob matching and the nested-subpackage check misbehaved on backslash paths. It's now built onPath::components().
All platforms (Linux, macOS, Windows) are now covered by CI on every push — the Windows and macOS suites run for the first time in this release's history, and are green.
No behavior changes on Linux or macOS. Windows users of any earlier version should upgrade.
Full Changelog: v0.1.4...v0.1.5