Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vue-splide fork makes lib usage behind proxy not possible #377

Closed
FabianWilms opened this issue Jan 15, 2025 · 2 comments · Fixed by #378
Closed

vue-splide fork makes lib usage behind proxy not possible #377

FabianWilms opened this issue Jan 15, 2025 · 2 comments · Fixed by #378
Assignees
Labels

Comments

@FabianWilms
Copy link
Member

With the newest release builds behind a proxy are not working anymore:

npm error code ENOTFOUND
npm error syscall getaddrinfo
npm error errno ENOTFOUND
npm error network request to https://codeload.github.com/joris-gallot/vue-splide/tar.gz/6f0199b1a3b09f943db07c7a2dedc9b6e4a917d0 failed, reason: getaddrinfo ENOTFOUND codeload.github.com
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly.  See: 'npm help config'
npm error A complete log of this run can be found in: [...]/.npm/_logs/2025-01-14T23_12_21_209Z-debug-0.log 

We should instead revert back to using the official npm package and patching it with patch-package as stated in #357 (comment)

Copy link

🎉 This issue has been resolved in version 2.1.1-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

🎉 This issue has been resolved in version 2.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant