Sp-dev-docs: Currently Windows exclusive but no support for Mac, Linux and Bash On Windows

[StfBauer]

Currently the new SharePoint Framework is Windows exclusive. The problem is caused when a file system is case-sensitive and not case-aware like Windows.

Got the following error message:

Currently it cannot reproduced on Bash for Windows because there is yet an unresolved issue with Yeoman generators.
To fix this issue you need to take care of correct written file names in all references.
Checked it on a partition that is case-insensitive and Yeoman generator is working perfectly.

[patmill]

Nick has a fix for this. It should roll in the next drop. We have people developing on Macs though. Are you running Linux, or a file system on the mac that is case sensitive?

[nickpape]

Hey, we just fixed this issue. A temporary workaround would be updating the casing of the imports.

In both @microsoft/sp-client-base/lib/index.d.ts, change:

./odataTypes/IOdataNavigationNodeCollection => ./odataTypes/IODataNavigationNodeCollection

./odataTypes/IOdataWeb => ./odataTypes/IODataWeb

In @microsoft/sp-client-preview/lib/local/bundles/platform-exports.d.ts:

../clientSideWebParts/propertyPane/propertyPaneFields/propertyPaneDropDown/IPropertyPaneDropdown => ../clientSideWebParts/propertyPane/propertyPaneFields/propertyPaneDropdown/IPropertyPaneDropdown

../clientSideWebParts/propertyPane/propertyPaneFields/propertyPaneDropDown/PropertyPaneDropDown => ../clientSideWebParts/propertyPane/propertyPaneFields/propertyPaneDropdown/PropertyPaneDropdown

../clientSideWebParts/propertyPane/propertyPaneFields/PropertyPaneTextField/PropertyPaneTextField => ../clientSideWebParts/propertyPane/propertyPaneFields/propertyPaneTextField/PropertyPaneTextField

Thanks!

[StfBauer]

Great will try this. The Bash On Windows issue I'm referring to is https://github.com/Microsoft/BashOnWindows/issues/468

You might add a comment just in case someone like to use it this way.

[StfBauer]

@nickpape-msft Thanx!!! Workaround works. Updated the files in the project after it have been provisioned it and got it running.

[StfBauer]

Sorry too fast. Just reopend it because it is not fixed in generator yet. Sorry.

[chakkaradeep]

Added the issue of node-gyp rebuild here in the known issues. Basically, you can ignore this as the bufferutil dependency uses JavaScript fallback if MSBUILD is not available, though it still outputs the error.

[StfBauer]

@chakkaradeep I my case it wasn't related to node-gyp. It was only related to case sensitive file systems. Most MacOS X installations don't have it anymore. Some still use (ok mostly web developers) it because the do regular web projects too and deploy it to Apache Web Server.
It is a big helper to get your file names right for any platform.

[chakkaradeep]

@StfBauer updated the doc with the workaround for the case sensitive file bug. Thanks!

[StfBauer]

Intermediate fix. ;)

All that needs to be done is to copy it over the @microsoft in node_modules.
It contains only the two affected node modules.

@microsoft.zip

[nickpape]

This has been fixed in the 9/2 release.

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues