Fail to build routes in Windows
See original GitHub issueDear contributors,
Thanks for this awesome project! 😃
After the recent update, I discovered voie is failing to build a route in my Windows machine. Quick jest run result is
C:\Users\10629\WebstormProjects\vite-plugin-voie\packages\vite-plugin-voie>npm test
> vite-plugin-voie@0.7.1 test
> jest
FAIL test/routes.spec.ts
√ given basic routes it should return the correct structure (3 ms)
√ given dynamic routes it should return the correct structure (1 ms)
√ given nested routes it should return the correct structure
√ given a catch-all route it should return the correct structure (1 ms)
√ given a glob as pagesDir and extend route it should resolve to correct path
× given a custom root, should return the correct component path (6 ms)
● given a custom root, should return the correct component path
expect(received).toEqual(expected) // deep equality
- Expected - 9
+ Received + 9
Array [
Object {
- "component": "/pages/index.vue",
- "name": "index",
- "path": "/",
+ "component": "/\\pages\\index.vue",
+ "name": "",
+ "path": "",
},
Object {
- "component": "/pages/user/index.vue",
- "name": "user",
- "path": "/user",
+ "component": "/\\pages\\user\\index.vue",
+ "name": "",
+ "path": "",
},
Object {
- "component": "/pages/user/one.vue",
- "name": "user-one",
- "path": "/user/one",
+ "component": "/\\pages\\user\\one.vue",
+ "name": "",
+ "path": "",
},
]
233 | root,
234 | });
> 235 | expect(actual).toEqual(expected);
| ^
236 | });
237 |
at Object.<anonymous> (test/routes.spec.ts:235:18)
Test Suites: 1 failed, 1 total
Tests: 1 failed, 5 passed, 6 total
Snapshots: 0 total
Time: 1.853 s, estimated 2 s
Ran all test suites.
npm ERR! code 1
npm ERR! path C:\Users\10629\WebstormProjects\vite-plugin-voie\packages\vite-plugin-voie
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c jest
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\10629\AppData\Local\npm-cache\_logs\2021-01-07T08_27_39_339Z-debug.log
I believe the problem occurs after the release 0.5 and using path.sep
inside routes.ts
and having actual set of Vue files as a test resource would be a remedy.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Why does this ROUTE ADD command fail? - Super User
You cannot have the loopback device (127.0.0.1) be the gateway. It doesn't make sense. What you are saying with this command is "route...
Read more >Default gateway route doesn't appear in Routing Table
Restart the remote access server. The default route for the re-added network interface is added to the Windows routing table.
Read more >custom route not working on windows - Server Fault
Windows will not try to route a packet to a 10/8 subnet (10.21/16 is a subnet of 10/8); there's no routing involved at...
Read more >Master Traceroute in Windows 10 for Fail-proof Route Tracking
You should recall that these packets also contain the TTL that causes the router to generate an error that contains information used by...
Read more >Adding a static route into the Windows routing table
This traffic will never make it to its destination and communications will fail. Today, we are setting up a new VPN server. This...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
A fix has been released in v0.7.2, please let me know if you see any more issues
Problems are totally gone. Appreciate it a lot @brattonross .