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
Cannot find module #20
Comments
I wonder if maybe it's a windows path issue. To rule out the content and if it's not too long, can you post the |
index.idl? I haven't changed it one bit. however when I open components.js, I see different slashes:
perhaps this is the issue. I'll try with different slahes. |
nope, doesn't help, because it's generated one I run app. here is index.idl content:
var code = true;
|
Ah, apologies. It's become a knee-jerk reflex to ask for full input before debugging output, but I think the issue is here. Specifically that it creates paths by adding a |
any way to help debug this? |
great. let me know and i'll test! |
See #20. I pushed… well, not so much a fix because I don't have a windows machine either, but it's at least a shot in the dark at replacing string-based path construction with @themre you might be able to clone, check out the branch, |
tried, got this error:
|
Thanks for testing! Hopefully that's progress. The line it points to is this: const components = fs.readdirSync(DEFAULT_COMPONENTS_FOLDER); I wonder if that needs to be something really explicit like |
like
|
Yeah, I don't think If it isn't obvious how to fix it, UW has some windows machines I can test on later today. |
Sorry, I meant const components = fs.readdirSync(path.join(process.cwd(), DEFAULT_COMPONENTS_FOLDER)); but I think it might require a closer look at the relative requires. |
I just merged #21, added automated testing in a windows environment, and released a patch on npm ( @themre let me know if you still have problems after this patch. To update either run |
It works!
Many thanks! |
hi,
I did a fresh install of idyll and yo. Ran yo idyll and npm start and got:
anyone else got this problem?
The text was updated successfully, but these errors were encountered: