You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
Not sure why, but this error just began on my project out of seemingly thin air.
warn Error on download for npm:ansi-styles
TypeError: Cannot read property 'tarball' of undefined
at NPMLocation.download (/Users/dmaddox/Documents/_ws/myproj/node_modules/jspm-npm/lib/npm.js:338:45)
at /Users/dmaddox/Documents/_ws/myproj/node_modules/jspm/lib/registry.js:117:30
at lib$rsvp$$internal$$tryCatch (/Users/dmaddox/Documents/_ws/myproj/node_modules/rsvp/dist/rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (/Users/dmaddox/Documents/_ws/myproj/node_modules/rsvp/dist/rsvp.js:1048:17)
at /Users/dmaddox/Documents/_ws/myproj/node_modules/rsvp/dist/rsvp.js:331:11
at lib$rsvp$asap$$flush (/Users/dmaddox/Documents/_ws/myproj/node_modules/rsvp/dist/rsvp.js:1198:9)
at _combinedTickCallback (node.js:376:9)
at process._tickCallback (node.js:407:11)
ansi-styles is the first package that my build process actually finds it wants to download, so I guess I might also fail on package 2, 3 etc. as well.
The parameters coming in to the download function are:
repo: 'ansi-styles'
version: '^2.1.0'
hash: ""
versionData: { }
This was first reported to me around 1:15 pacific time on a build that seemed fine yesterday and I believe was fine earlier today as well.
???
The text was updated successfully, but these errors were encountered:
Not sure why, but this error just began on my project out of seemingly thin air.
ansi-styles is the first package that my build process actually finds it wants to download, so I guess I might also fail on package 2, 3 etc. as well.
The parameters coming in to the download function are:
This was first reported to me around 1:15 pacific time on a build that seemed fine yesterday and I believe was fine earlier today as well.
???
The text was updated successfully, but these errors were encountered: