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 Oct 1, 2020. It is now read-only.
It looks like electron-compile is depending on a private NPM package, which has now been made public. On the NPM page for "@paulcbetts/mime-types" it recommends installing with:
npm install --save mime-types
But instead, we still have @paulcbetts/mime-types in the package.json.
When I try to install, this is what happens. Any help on how to fix this (aside from forking, modifying, and re-building the package)?
jblalock-0038:synack-desktop jeremy$ npm install --save-dev electron-prebuilt-compile
npm ERR! Darwin 15.2.0
npm ERR! argv "/Users/jeremy/.nvm/versions/node/v5.5.0/bin/node" "/Users/jeremy/.nvm/versions/node/v5.5.0/bin/npm" "install" "--save-dev" "electron-prebuilt-compile"
npm ERR! node v5.5.0
npm ERR! npm v3.9.3
npm ERR! code E404
npm ERR! 404 no such package available : @paulcbetts/mime-types
npm ERR! 404
npm ERR! 404 '@paulcbetts/mime-types' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'electron-compile'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/jeremy/Documents/Synack/Code/experiments/synack-desktop/npm-debug.log
The text was updated successfully, but these errors were encountered:
It looks like
electron-compile
is depending on a private NPM package, which has now been made public. On the NPM page for "@paulcbetts/mime-types" it recommends installing with:But instead, we still have
@paulcbetts/mime-types
in the package.json.When I try to install, this is what happens. Any help on how to fix this (aside from forking, modifying, and re-building the package)?
The text was updated successfully, but these errors were encountered: