Forums Indigo.Design
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Wesley Hull
15
Code Generation using VSCode extension fails
posted

Hello,

We are exploring Indigo Design and have tried to generate Angular code(via isual Studio Code extension) for the Sketch file uploaded and published to Indigo Design.
When we import the URL into the extension, the code generation updates existing files such as package.json/angular.json but does not generate any components/modules for the sketch file.

Following are the errors we see in the extension.log:

[3/22/2019 17:50:17] [Info] Successfully generated code.
[3/22/2019 17:50:18] [Info] Executing subprocess 'ng g module infragistics-imports --dry-run=false' with working directory /Users/wes/appindigotest/indigo-app
[3/22/2019 17:50:18] [Info] 'ng g module infragistics-imports --dry-run=false' exited with code 127
[3/22/2019 17:50:18] [Error] Module InfragisticsImportsModule failed to generate.
[3/22/2019 17:50:18] [Info] Executing subprocess 'ng g module negotiate-page --routing --dry-run=false' with working directory /Users/wes/appindigotest/indigo-app
[3/22/2019 17:50:18] [Info] 'ng g module negotiate-page --routing --dry-run=false' exited with code 127
[3/22/2019 17:50:18] [Error] Module NegotiatePageModule failed to generate.
[3/22/2019 17:50:18] [Info] Executing subprocess 'ng g module negotiate-page/negotiate-page-routing --flat --dry-run=false' with working directory /Users/wes/appindigotest/indigo-app
[3/22/2019 17:50:18] [Info] 'ng g module negotiate-page/negotiate-page-routing --flat --dry-run=false' exited with code 127
[3/22/2019 17:50:18] [Error] Routing module NegotiatePageModule failed to generate.
[3/22/2019 17:50:18] [Info] Executing subprocess 'ng g component negotiate-page/negotiate-component --module negotiate-page --dry-run=false' with working directory /Users/wes/appindigotest/indigo-app
[3/22/2019 17:50:18] [Info] 'ng g component negotiate-page/negotiate-component --module negotiate-page --dry-run=false' exited with code 127
[3/22/2019 17:50:18] [Error] Component files were not generated for negotiate-component component.


There are also error in the customer-messages.log:
Customer Information Messages for blob.sketch

Symbol not found parent name: No parent, class name: symbolInstance, Object name: Terms List, symbolId: DA1E9828-D85E-4298-A0B8-D65E78B60B6C, this object will not be rendered.
Symbol not found parent name: No parent, class name: symbolInstance, Object name: Comments, symbolId: A0DA7DEA-0103-4D3F-9484-D450F0B7AE6A, this object will not be rendered.

In addition to this, we do have a question on the Ignite UI for Angular. Would it be possible to use native Material components in addition to the Ignite UI Angular components?

Regards,
Wes

Parents
  • 34510
    Offline posted

    Hi Wes,

    From the log I can see that the Angular CLI commands failed to execute.  I believe code 127 means the command could not be found on your system which means the system doesn't have the Angular CLI globally installed.  You can check this by opening a terminal program like bash or command prompt and typing "ng" without the quotes.  If it says it doesn't recognize the command then you will need to install the Angular CLI globally.

    You can do this by running  the "npm install -g @angular/cli" command in your terminal program.  Once that has completed try using our VS Code Extension again.

    As for using native Material components, I believe you can but I will need double check with the Ignite UI team before I'm 100% sure.  I will let you know when they get back to me.

Reply Children
No Data