-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Can't Scaffold a Full Stack App (Cannot find module 'regenerator/runtime') #1518
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
Comments
Maybe there was a problem installing the generator. Try re-installing it. |
So I re-installed all the components and it looked like it worked but after scaffolding an app and when I run grunt serve for preview the browser would show Failed to load resource: net::ERR_EMPTY_RESPONSE, which is actually browser has received No Data, I have my mongodb running. Do you know how to get around this? |
Same issue here. Please help us. |
Do you still have this problem? |
I don't have the same problem as discussed in this thread but a different one maybe manifestation of something related, I got around this issue by reinstalling all the components but now my App never runs, though there are no errors but the localhost:9000 will show a page that tells NO_RESPONSE which means something is wrong with the network settings but actually that is not the case. I tried on different connections, PCs, macbook, using VPS but my app will never load, I think I talked about that issue in a separate thread |
You get this with a freshly-generated app? I don't think I've ever seen that before. Do you have more details? |
Yes, I got away from this problem Can't Scaffold a Full Stack App (Cannot find module 'regenerator/runtime') by reinstalling all the things from scratch, like yo, grunt-cli, bower et-al... |
I'm talking about the |
I have never been able to get around ERR_EMPTY_RESPONSE. It still exists. |
Please share some more details |
I have mentioned everything here, Since I don't have any console errors or anything like that, please refer this link, This has all the details. Not sure what else you need. |
What happens if you change directories and scaffold out a brand new app, and then run |
I haven't tried it recently since the last issue #1628 was reported but during that time I have tried almost everything, new directories, new app names, using a combinations of selections while generating app, like dropping Socket.io, Mongoose vs Sequel, grunt vs gulp, jade vs html, different authentications and all that and nothing worked for me and I finally gave up on this generator and I found another pretty basic generator bangular. However that said I am going to give it another shot using a latest git pull. Rest assured, I did almost everything to get this working but it just didn't; I know it doesn't look like a generator bug most likely, and looks like a network issue
but I tried it on 2/3 ISPS, home network, office network, used proxies as well as vpns, mac as well as pc but no luck. That said I am going to give it another shot and will let you know if there is anything specific to report. |
Just to make sure, can you respond with which versions of these you're using? generator-angular-fullstack |
I can't check right now but if my memory server right here is the approximation Node 4.6+ |
Okay so I have the stable node verison v.5.2.0 and I installed the latest yo, grunt-cli as well as bower but once i hit yo angular-fullstack sampleFirstApp, I get the following error, any ideas:
module.js:329
throw err;
^
Error: Cannot find module 'regenerator/runtime'
at Function.Module._resolveFilename (module.js:327:15)
at Function.Module._load (module.js:278:25)
at Module.require (module.js:355:17)
at require (internal/module.js:13:17)
at Object. (/usr/local/lib/node_modules/generator-angular-fullstack/node_modules/babel-core/lib/polyfill.js:5:1)
at Module._compile (module.js:399:26)
at Object.Module._extensions..js (module.js:406:10)
at Module.load (module.js:345:32)
at Function.Module._load (module.js:302:12)
at Module.require (module.js:355:17)
at require (internal/module.js:13:17)
The text was updated successfully, but these errors were encountered: