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

Register plugins failed from electrode app server #28

Closed
ajaxdinesh opened this issue Jan 16, 2018 · 3 comments
Closed

Register plugins failed from electrode app server #28

ajaxdinesh opened this issue Jan 16, 2018 · 3 comments

Comments

@ajaxdinesh
Copy link

ajaxdinesh commented Jan 16, 2018

I am new for Electrode. I tried to implement 'electrode-app as per the document. When i run the below command after created electrode-app folder and got an error message as mentioned in the below image. Could you please help me to fix this issue?
$ clap dev
image

@daljitsumman
Copy link

Hi there

I too am having the exact same problem - as well as all the developers I work with. We are considering the use of electrode for use in the next gen architecture for front end. Due to it being an enterprise environment we have to use Windows machines.

Also after the 'ignite generate-app' command, the process failed to install some modules which had to be installed by using 'yarn install' within the project directory.

Webpack does not seem to be transpiling the jsx files in client and server folders.

Thanks for your help - we would really like to use electrode, but currently this is completely stopping us.

I have attached some screenshots of the problem
electrode problems
windows information

@ajaxdinesh
Copy link
Author

Thanks for your information. I installed node version >9.0 and yarn not supported during the installation. So i downgrade the version 8.0.0 and re-generate the electrode app and now working fine.

@daljitsumman
Copy link

Thanks Ajaxdinesh

I had tried downgrading but my issue was i didnt go back far enough.

I can confirm that by reducing the node version installed on the machine to 8.0.0 ( I used NVM ) it does indeed work and the import failures have disappeared.

Thanks for pointing me in the right direction regarding this problem, well done in finding that fix.

I am however slightly concerned that I could not find this information was not available in any of the documentation - and if it were, it was not upfront and center. When choosing to use frameworks like this, if automated generators do not work because of obscure problems it causes a huge dent in confidence of that product (what else could go wrong down the line?)

working hapijs

@jchip jchip closed this as completed Nov 12, 2019
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

3 participants