-
Notifications
You must be signed in to change notification settings - Fork 20
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 'xregexp' #11
Comments
I’m running into this as well. |
xregexp should behave as expected again. I'm looking into moving to 'scoped npm modules' so that I can get rid of the github#master references and still have a fast turn-around while developing. |
…ases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11
…ases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11
…ases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11
I just ran npm install https://github.com/GerHobbelt/jison/archive/0.4.18-186.tar.gz
node_modules/jison-gho/lib/cli.js node_modules/jison-gho/examples/ansic.jison on macOS 10.12.6 and still get
|
…ype and OpaqueType. - bumped build revision and moving towards public 'scoped package' releases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11
…pmjs.com/misc/scope; this is also related to GerHobbelt/jison#11
…s as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11
… releases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11
…ases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11 -- rant: this need to change every bloody `require()` call in the code for a 'scoped package' is what I particularly dislike about this approach, but so far, it's the best we've got as long as the entire world hasn't upgraded to packge-lock.json support... /rant
…pmjs.com/misc/scope; this is also related to GerHobbelt/jison#11 -- rant: this need to change every bloody `require()` call in the code for a 'scoped package' is what I particularly dislike about this approach, but so far, it's the best we've got as long as the entire world hasn't upgraded to packge-lock.json support... /rant
…ases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11 -- rant: this need to change every bloody `require()` call in the code for a 'scoped package' is what I particularly dislike about this approach, but so far, it's the best we've got as long as the entire world hasn't upgraded to packge-lock.json support... /rant
…pmjs.com/misc/scope; this is also related to GerHobbelt/jison#11 -- rant: this need to change every bloody `require()` call in the code for a 'scoped package' is what I particularly dislike about this approach, but so far, it's the best we've got as long as the entire world hasn't upgraded to packge-lock.json support... /rant
… as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11 -- rant: this need to change every bloody `require()` call in the code for a 'scoped package' is what I particularly dislike about this approach, but so far, it's the best we've got as long as the entire world hasn't upgraded to packge-lock.json support... /rant
…ndencies listed in package.json. This is also related to GerHobbelt/jison#11.
…ases as per https://docs.npmjs.com/misc/scope; this is also related to GerHobbelt/jison#11 -- rant: this need to change every bloody `require()` call in the code for a 'scoped package' is what I particularly dislike about this approach, but so far, it's the best we've got as long as the entire world hasn't upgraded to packge-lock.json support... /rant
…ndencies listed in package.json. This is also related to GerHobbelt/jison#11.
… they get copied into lib/util/ - patched all `require()` statements in the examples as well to match the 'scoped package' dependencies listed in package.json. This is also related to #11. Grmbkl!@#$%^&*! - jison modules DO NOT belong in the **dependencies**, but should reside in the **devDependencies**. Where I screwed this up, I don't know (git blame should hand me the answer to that but I'll do that later when I feel like it), but now that we move towards 'scoped packages' it's biting me in the aXX! :-( - regenerated library files
WARNING: work is underway to solve this, but be reminded that build 0.6.0-187 still hasn't been round-trip tested, so expect another release after that one before this can be said to be 'solved'. |
|
…hingamajig. **censored** this is also related to GerHobbelt/jison#11
Okay, I think I've got it nailed now. Notes on that release:
|
@stefan-leye : Thanks! |
fixed in latest release 0.6.0-191; jison dependencies now use scoped packages where necessary (https://docs.npmjs.com/misc/scope) plus npm's |
@stefan-leye: ping? Can we confirm this fixed with -191 or later? (FYI: I've switched to using scoped packages for the submodules so this type of problem should be gone or at least severely mitigated in the future.) |
@GerHobbelt ah sorry, for not replying. I switched to an older version of jison, that works for our project. |
Thanks for the info, I'll keep it open then until you get an opportunity to verify. (Off-topic: I hope to have some more work done on jison by November -- fingers crossed 😉 -- so it would be great to hear about your experience then. (the main issue now is documentation; others using this helps as a strong motivator to give that one a fresh shove in the gluteus maximus) |
@GerHobbelt finally tried it out. Everthing works fine :) |
Superb! 👍 I'm going to close this issue; if anything pops up, please create a new one and reference this one (or re-open this issue). Enjoy! |
Since yesterday I get the error message: "Cannot find module 'xregexp'", when using the parser generator.
A bit of investigation showed that the xregexp dependency points to the master of a forked xregexp lib, that has been changed in the last hours.
I think we have two issues here:
The text was updated successfully, but these errors were encountered: