-
Notifications
You must be signed in to change notification settings - Fork 6
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
Build ERROR : Cannot read property 'ACCOUNT' of undefined #13
Comments
@jonterrylee can you please help on this |
Looks like you might be using an old/bad version. Let me take a look. |
@jonterrylee No , we are using the latest version. |
@jonterrylee can you please help on this . because of this error we cannot use the latest version 2.0. We have reverted to V 1.4. Looking for your prompt action on this. |
Sorry we have been swamped and haven't had the time to fix this issue. We would need to update the generator to support version 2.0. We are unfortunately at a conference this week but we will try to address this in the upcoming weeks. |
The problem appears to be in config.js ->
|
@JayakrishnanJK - Did you figure this out? |
@cmthomps No actually . now we are using thr old versionV 1.4. because of this error we cannot use the latest version 2.0. We have reverted to V 1.4. |
Hi! I had to add the following: |
yarn run v1.3.2
$ cross-env NODE_ENV=development; node scripts/nodemon;
/srv/src/src/config.js:70
[RESOURCES.ACCOUNT]: {
^
TypeError: Cannot read property 'ACCOUNT' of undefined
at Object. (/srv/src/src/config.js:70:14)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
at Module.require (module.js:587:17)
at require (internal/module.js:11:18)
at Object. (/srv/src/src/index.js:5:5)
at Module._compile (module.js:643:30)
Nodemon crashed. Waiting for changes to restart.
We are getting this error while trying to build the fhir facade .
Please help on this.
The text was updated successfully, but these errors were encountered: