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

Installing then requiring the module results in error #24

Open
ashnur opened this issue Feb 8, 2016 · 6 comments
Open

Installing then requiring the module results in error #24

ashnur opened this issue Feb 8, 2016 · 6 comments

Comments

@ashnur
Copy link

ashnur commented Feb 8, 2016

Error: Cannot find module 'type' from '/home/ashnur/foo/node_modules/jsedn/lib'
@Samstiles
Copy link

👍 @shaunxcode any ideas?

@npfitz
Copy link

npfitz commented Mar 15, 2016

@ashnur not sure if you're still stuck on this or not, but I was running into the same issue. Looks like it was trying to bring in something from component.js and getting a little confused or sad. I was able to fix the issue by doing the following:

  • adding "component-type": "latest" to package.json
  • inside type.coffee, changing require "type" to require "component-type"
  • rebuilding
  • npm linking the project

You may need to fork this project and have npm point at your fork rather then the npm repo (until this gets resolved).

Hope this helps!

@kristianmandrup
Copy link

Please make a pull request or a fork where it works :) Anyone?

@ashnur
Copy link
Author

ashnur commented Mar 26, 2016

@kristianmandrup have you tried @npfitz 's suggestions?

@yedi
Copy link

yedi commented Sep 6, 2017

I am also having this issue. I'm not exactly sure i get all of @npfitz instructions.

Are they saying that I should download my own copy of jsedn, make that modification and then npm link my local copy?

I feel like I'm doing something wrong -- seems weird that the recommended edn library in JS can't actually be required and used when installed via npm.

@npfitz
Copy link

npfitz commented Sep 7, 2017

@yedi Admittedly, it's probably a terrible suggestion (though I've been running with that change for a while now). What I did was make my own fork of the project, made my change, and then just pointed to NPM to my fork.

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

5 participants