GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Module fails to load · Issue #299 · nodegit/nodegit

Module fails to load #299

New issue
Copy link
New issue
Copy link
Closed
Closed
Module fails to load#299
Copy link

Description

@lavelle
lavelle
opened on Nov 26, 2014
Issue body actions

When I try to import the library I get the error Cannot find module '../build/Debug/nodegit'.
I looked at the source and saw that it only tries to do this when loading the release version failed. I logged the error that is caused by loading the release version, and got Module did not self-register..

Do you know what this means and how I can fix it?

Activity

  1. johnhaley81 commented on Nov 26, 2014

    @johnhaley81
    johnhaley81
    on Nov 26, 2014
    Collaborator
    More actions

    Are you trying to load this in node-webkit?

  2. maxkorp commented on Nov 26, 2014

    @maxkorp
    maxkorp
    on Nov 26, 2014
    Collaborator
    More actions

    It probably didn't build correctly. How did you grab the module, via NPM? if so, try cding into the directory and running an NPM install

  3. lavelle commented on Nov 26, 2014

    @lavelle
    lavelle
    on Nov 26, 2014
    Author
    More actions

    @johnhaley81 yeah, are there known issues with that?

  4. maxkorp commented on Nov 26, 2014

    @maxkorp
    maxkorp
    on Nov 26, 2014
    Collaborator
    More actions

    Ha, yes (thats how we ended up involved in nodegit). You have to rebuild with nw-gyp, currently nodegit builds with node-gyp

  5. lavelle commented on Nov 26, 2014

    @lavelle
    lavelle
    on Nov 26, 2014
    Author
    More actions

    oh yeah I think I remember having to use that to get another lib with a native extension to work before. Is there a way to do it automatically as part of the install process? My library which depends on nodegit is consumed by a regular Node CLI and node-webkit GUI, so I'd like to get a system which works for both.

  6. maxkorp commented on Nov 26, 2014

    @maxkorp
    maxkorp
    on Nov 26, 2014
    Collaborator
    More actions

    We actually have an issue for that, I've found a few strategies for detecting node-webkit, but one needs to be implemented and used to have it gyp with the correct tool.

  7. maxkorp commented on Nov 26, 2014

    @maxkorp
    maxkorp
    on Nov 26, 2014
    Collaborator
    More actions

    #212

  8. lavelle commented on Nov 26, 2014

    @lavelle
    lavelle
    on Nov 26, 2014
    Author
    More actions

    Ah okay well if there's a fix coming soon then I might just keep testing it with the CLI and integrate with the GUI once that works.

  9. johnhaley81 commented on Nov 26, 2014

    @johnhaley81
    johnhaley81
    on Nov 26, 2014
    Collaborator
    More actions

    Yeah we're working on a fix now since that's pretty big and important :)

    Closing this since we already have an issue tracking this. If you want to discuss this further, feel free to over at #212.

  10. johnhaley81
    closed this as completedon Nov 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.