SOLVED

SPFx with Visual Studio 2015

Highlighted
Occasional Contributor

Hi everyone!

I'm playing with SPFx by doing some "hello world" apps, and everything is working fine for now. But, I'm having an issue when I try to run my open my code with Visual Studio 2015 instead of Visual Studio Code. It seems that I need a module called "\node_modules\@microsoft\npmx\lib\gulp2vs.js", but I'm unable to get it. I have tried to reinstall node tools for VS, I've installed the latest update for VS 2015 (Update 3) also, but I'm stuck with this Error.

Does anyone run SPFx project inside VS 2015 without problems?

Thank you in advance :)

2 Replies
Highlighted
Solution

It seems that using the latest released drop of SPFx the problem disappears. Now I can build and run my code with VS 2015 following the instructions here: http://dev.office.com/sharepoint/docs/spfx/web-parts/basics/use-visual-studio.

 

Latest drop that worked for me: https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-Drop-3

 

Thanks SPFx team!

Highlighted

it seems like the latest Drop 4 and MDL2 was broken under VS2015. I got the following error message when run gulp serve:

[23:01:44] Error - typescript - src\webparts\helloWorld\HelloWorldWebPart.d.ts(6,14): error TS1005: '=' expected.

[23:01:44] Error - typescript - src\webparts\helloWorld\HelloWorldWebPart.d.ts(6,34): error TS1005: ';' expected.

[23:01:45] Error - 'typescript' sub task errored after 6.47 s "TypeScript error(s) occurred."

[23:01:45] 'serve' errored after 9.71 s

[23:01:45] Error - typescript - src\webparts\helloWorld\HelloWorldWebPart.d.ts(6,14): error TS1005: '=' expected.Error - typescript - src\webparts\helloWorld\HelloWorldWebPart.d.ts(6,34): error TS1005: ';' expected.Error - 'typescript' sub task errored after 6.47 

 

The line 6 on HelloWorldWebPart.d.ts is

    readonly propertyPaneSettings: IPropertyPaneSettings;

Other than that, the line 8 in HelloWorldWebPart.ts alway showed the error message for import scss.

 

import styles from './HelloWorld.module.scss';

 

Anyone know the workaround?