Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to activate the json-schema package #12

Open
brad-jones opened this issue Oct 1, 2015 · 2 comments
Open

Failed to activate the json-schema package #12

brad-jones opened this issue Oct 1, 2015 · 2 comments

Comments

@brad-jones
Copy link

Looks like the package "loophole" has not been saved to the package dependencies list.
I navigated to .atom\packages\json-schema and ran npm install loophole and this appears to fix the issue.

[Enter steps to reproduce below:]

  1. Updated to v0.1.14
  2. Opened Atom

Atom Version: 1.0.19
System: Microsoft Windows 8.1 Pro
Thrown From: json-schema package, v0.1.14

Stack Trace

Failed to activate the json-schema package

At Cannot find module 'loophole'

Error: Cannot find module 'loophole'
    at Module._resolveFilename (module.js:334:15)
    at Function.Module._resolveFilename (C:\Users\Brad\AppData\Local\atom\app-1.0.19\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 C:\Users\Brad\.atom\packages\json-schema\lib\schema-linter.js:3:20
    at Object.<anonymous> (C:\Users\Brad\.atom\packages\json-schema\lib\schema-linter.js:8:3)
    at Module._compile (module.js:428:26)
    at Object.defineProperty.value [as .js] (C:\Users\Brad\AppData\Local\atom\app-1.0.19\resources\app.asar\src\compile-cache.js:169:21)
    at Module.load (module.js:353:32)
    at Function.Module._load (module.js:308:12)
    at Module.require (module.js:363:17)
    at require (module.js:382:17)
    at JsonSchema.provideLinter (C:\Users\Brad\.atom\packages\json-schema\lib\json-schema.js:41:30)
    at Package.module.exports.Package.activateServices (C:\Users\Brad\AppData\Local\atom\app-1.0.19\resources\app.asar\src\package.js:416:69)
    at Package.module.exports.Package.activateNow (C:\Users\Brad\AppData\Local\atom\app-1.0.19\resources\app.asar\src\package.js:248:16)

Commands

Config

{
  "core": {
    "themes": [
      "atom-dark-ui",
      "monokai-soda"
    ],
    "disabledPackages": [
      "open-last-project",
      "autocomplete-snippets"
    ]
  }
}

Installed Packages

# User
.bin, vundefined
atom-yeoman, v0.3.15
docblockr, v0.7.3
json-schema, v0.1.14
line-ending-converter, v1.3.2
linter, v1.7.2
monokai-soda, v0.5.0
omnisharp-atom, v0.24.14
pretty-json, v0.4.1

# Dev
No dev packages
@RyanBreaker
Copy link

Same issue here and the mentioned fix makes it work for me.

peterblazejewicz added a commit to peterblazejewicz/atom-json-schema that referenced this issue Oct 1, 2015
This commit add missing loophole module dependency
fixing problem in Atom editor as described in OmniSharp#12
@jerone
Copy link

jerone commented Nov 6, 2015

This seems to be fixed by 82b38db

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants