Derk-Jan Karrenbeld
Derk-Jan Karrenbeld
(to respond to my comment about windows: I meant the implementation before this PR.)
Still on the list, I think I have a solution. Will try to test it some more ~this~ next week.
Yap. Ping me again on Friday if I haven't pushed yet.
Was able to empty my friday out so I'll work on this tomorrow! *Edit*: Working on it as we speak. Will be a few hours as I want to do...
Same as: https://github.com/nrwl/precise-commits/issues/7
Here is the patch-package until it's fixed upstream: ```diff diff --git a/node_modules/@11ty/eleventy-plugin-vite/EleventyVite.js b/node_modules/@11ty/eleventy-plugin-vite/EleventyVite.js index cb546a0..5e785ad 100644 --- a/node_modules/@11ty/eleventy-plugin-vite/EleventyVite.js +++ b/node_modules/@11ty/eleventy-plugin-vite/EleventyVite.js @@ -49,7 +49,10 @@ class EleventyVite { let tmp =...
This is not the reason #22 happens. With outputDir: `dist`, this still happens.
My patch still works
I do think there may be an issue remaining. Whilst the sentry fix made my Windows builds work again, they do (still) hand on Gitlab CI. I also tested that...
Would it be using the local expo package for that? That's at 50.0.19. on the ci it uses the latest eas-cli, and no expo-cli is globally installed.