vite-plugin-remote-assets 2.1.0
Bundles your assets from remote urls with your app
vite-plugin-remote-assets@2.1.0 was published on 2025-08-18. Its manifest declares 4 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All vite-plugin-remote-assets versions · Permanent reference to 2.1.0 · View npm registry JSON · Latest release
Package specifications
| Version | 2.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2025-08-18T05:44:30.045Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 4 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 10.11 KiB |
| Published file count | 5 |
| Package type | module |
| ES module entry | dist/index.mjs |
| Default entry | dist/index.mjs |
| Side effects declaration | false |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install vite-plugin-remote-assets 2.1.0
npm install vite-plugin-remote-assets@2.1.0 pnpm add vite-plugin-remote-assets@2.1.0 yarn add vite-plugin-remote-assets@2.1.0
Runtime dependencies
- debug ^4.4.1
- magic-string ^0.30.17
- node-fetch-native ^1.6.7
- ohash ^2.0.11
Peer requirements
- vite >=5.0.0
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @jridgewell/sourcemap-codec@1.6.0 — indirect
- debug@4.4.3 — direct
- magic-string@0.30.21 — direct
- ms@2.1.3 — indirect
- node-fetch-native@1.6.7 — direct
- ohash@2.0.12 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-10T06:10:58.139Z
- https://api.deps.dev/v3/systems/npm/packages/vite-plugin-remote-assets/versions/2.1.0:dependencies — retrieved 2026-11-10T03:09:17.274Z
- https://api.deps.dev/v3/systems/npm/packages/vite-plugin-remote-assets/versions/2.1.0 — retrieved 2026-11-10T06:10:58.223Z