sveale / remote-edit

remote-edit
MIT License
146 stars 55 forks source link

Failed to load the remote-edit package #129

Closed lvnilesh closed 8 years ago

lvnilesh commented 8 years ago

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 1.0.15 System: Mac OS X 10.10.5 Thrown From: remote-edit package, v1.8.20

Stack Trace

Failed to load the remote-edit package

At Cannot find module 'serializable'

Error: Cannot find module 'serializable'
    at Module._resolveFilename (module.js:334:15)
    at Function.Module._resolveFilename (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/module-cache.js:383:52)
    at Function.Module._load (module.js:284:25)
    at Module.require (module.js:363:17)
    at require (module.js:382:17)
    at Object.<anonymous> (/Users/cloudgenius/.atom/packages/remote-edit/lib/model/remote-edit-editor.coffee:20:18)
    at Object.<anonymous> (/Users/cloudgenius/.atom/packages/remote-edit/lib/model/remote-edit-editor.coffee:255:4)
    at Module._compile (module.js:428:26)
    at Object.defineProperty.value [as .coffee] (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:169:21)
    at Module.load (module.js:353:32)

Commands

Config

{
  "core": {
    "themes": [
      "one-light-ui",
      "solarized-light-syntax"
    ]
  }
}

Installed Packages

# User
atom-alignment, v0.12.1
emmet, v2.3.12
highlight-selected, v0.10.1
remote-edit, v1.8.20

# Dev
No dev packages
sveale commented 8 years ago

Have you tried reinstalling the package?

lvnilesh commented 8 years ago

no I just uninstalled it. I will install it again.

sveale commented 8 years ago

Did it resolve the issue?

gmemstr commented 8 years ago

I can confirm that reinstalling it does not fix the issue.

EDIT: This is a bit odd... this was reported a long time ago but it's just started happening to me.

sveale commented 8 years ago

If anyone still having issues with this, it might be related to #143 which should now be resolved.

gmemstr commented 8 years ago

@sveale I posted my issue separately, it was #138, which you resolved.

sveale commented 8 years ago

@gmemstr allright thanks. I'll close this issue also then :)