Skip to content

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

@FabianWilms

Description

@FabianWilms

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)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions