[labs/eleventy-plugin-lit] Test suite fails in Windows
- Dominant language
- TypeScript
- Stars
- 21.8k
- Forks
- 1.1k
- Avg merge
- 18h 25m
- Merged PRs (30d)
- 2
Description
### Which package is this a feature request for?
Eleventy Plugin (@lit-labs/eleventy-plugin-lit)
### Description
Running the test for `labs/eleventy-plugin-lit` on a Windows machine fails with some permission errors.
Certain Windows user config will see:
```
EPERM: operation not permitted, symlink
```
Running as administrator or enabling Developer Mode in Windows does allow symlink but then all tests besides the first one fails with
```
EPERM: operation not permitted, stat
```
pointing to `node_modules\@lit-labs\eleventy-plugin-lit` within the temp directory created for each test.
Possibly issue with how symlinks are made? Might be worth checking out wireit's handling of symlinking for Windows.
### Alternatives and Workarounds
N/A
Contributor guide
Research direction
The failing area is labs/eleventy-plugin-lit, whose tests create a temporary directory containing node_modules\@lit-labs\eleventy-plugin-lit; start by running that suite on Windows and inspect Wireit's symlink handling. Done means the suite passes for regular users, including without administrator privileges or Developer Mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100