10

In the 0.1.0 version of @microsoft/generator-sharepoint it has started setting gulp serve to use https. This is the right approach so you don't have to set your browser to allow unsafe scripts, but for this to work properly you have to configure certificates. I guess we'll get a nice description of how to configure this rightly, but for now the easiest ...


8

The workbench.aspx inherits from Microsoft.SharePoint.WebControls.ClientSidePage which I assume uses the specified ClientSideApplicationId to load a specific Client Side Application. The id 8be81a5c-af38-4bb2-af97-afa3b64dfbed is the Workbench app which as part of the html includes: <script type="text/javascript" src="https://spoprod-a.akamaihd.net/...


8

In SPFX GA version the ModuleLoader was renamed to SPComponentLoader. import { SPComponentLoader } from `'@microsoft/sp-loader'; It continues to be userd in constructor: constructor() { super(); SPComponentLoader.loadCss('...'); } Please check the reference reply:


7

The easiest way to do this would be to load the data in your OnInit() method, and then reference it in your property pane. That won't work if you need the data to be more reactive (ie, you first select a list, then you select a list item), but if you are simply showing the current set of lists in the current web (for example), that should work. We need ...


7

Neither Gulp or Node act as the web server. The web server used for SPFx is Connect, see below. These are (some of) the different moving parts in the SPFx workbench Node.js: is the JavaScript runtime, using Chrome V8 JavaScript engine (could be compared to .NET CLR) Gulp: is a build system for Node.js (also known as a task runner) Gulp-connect: is a Gulp ...


7

Short answer - no, it's not required. Longer answer - The toolchain we'll provide and invest in will be TypeScript based, as that is what we use internally for our own work, and we've found that it is better for us to focus on one solution than spread out across many. That said, the plan is to a) create additional documentation on what the final output ...


6

SPFx webparts are JavaScript so, yes, you can reverse engineer them. If you load a client-side webpart and use F12 browser tools you can see the code which is bundled into a big JavaScript file by webpack, but the webpart code is near the top and you can easily find it and breakpoint it if needed. At worst you might face minification and obfuscation. ...


6

Most likely cause is the NPM folder is missing from the PATH declaration, so it can not find the commands installed in the NPM folder For Windows: Check if everything is correctly installed Execute in a command prompt: dir %appdata%\npm\*.cmd /b This should list the available commands: Execute the Yeoman SharePoint Generator %appdata%\npm\yo @...


6

Update to node package manager (npm) 3 using npm -g install npm@next and your path length issues should go away This is because the LTS version of node ships with npm v2.x whereas npm 3.x has better package handling and doesn't create such deeply nested folders.


6

The easiest way to load CSS from CDN is using the ModuleLoader class. First you import ModuleLoader in your code: import ModuleLoader from '@microsoft/sp-module-loader'; Then, in the web part's constructor you use it to load the CSS file from CDN: public constructor(context: IWebPartContext) { super(context); ModuleLoader.loadCss('https://maxcdn....


6

SPFX webparts will not have any server side code and it is all written in Javascript/typescript with Calls made to SharePoint using REST API or using JSOM. But if you need to write some server side code for e.g.: query something from external database or for some other scenario, then you need to create an ODATA Rest WebAPI for it and consume it in your SPFX ...


6

The mystery is solved. The typescript version is pulled in by tslint and in turn by the internal gulp-related typescript. The output of "TypeScript version: 2.1.6" happens when the tslint task starts a typescript compilation: Looking at the "package.json" in "node_modules/@microsoft/sp-tslint-rules" I can see this typescript dependency: "@microsoft/gulp-...


6

Workflow is not supported in SharePoint Framework. Use PnP or Microsoft Flow instead.


6

The latest OUIFR release is not compatible with SPFX at this point. You should install version 4.28.0 of OUIFR.


5

No, that is not possible at this time. Interesting idea though. Can you as it a feature request to the github issue list?


5

As soon as you do your first successful build, that error in the IDE should go away. See this issue in github - https://github.com/SharePoint/sp-dev-docs/issues/22


5

So, you're using React as your JavaScript framework, if you don't have a lot of experience with React and how it works I'd suggest you to first read more about it and play with it outside the new SharePoint framework, that will ensure that you understand the basic concepts without being overwhelmed with all the technologies in the new framework. In your ...


5

As Eric mentioned, no. You can't do this, and you won't be able to do this directly from the browser, as anything the browser can do, anyone else can do. What you would want to do is the following (this will be somewhat complex) 1 - Create an Azure App that has the permissions that you are wanting to elevate to, and hook up the auth flow so that you can ...


5

To do CRUD operations with SharePoint lists and libraries, you can take a look at the GitHub sample by Waldek Mastykarz. The sample does CRUD operations on SharePoint lists using multiple frameworks like React, Angular, PnP js and simple NoScript sample as well. It will give you a basic idea to create , update and delete items in the SharePoint list. The ...


4

SPFx development can only be done with (thorough) TypeScript knowledge (and the whole dev stack) No I have gone from no knowledge to producing proof of concept code for a relatively complex scenario (export search results to CSV) in a week. The 'whole' dev stack is not too bad but you will need to understand npm, gulp, typescript and preferable REACT. ...


4

noop it for now by adding this before any of the SPFx stuff gets loaded. console.log(// extra wrapper so below code is taken out on minification (function() { var noop = function noop() {}; var methods = [ 'assert', 'clear', 'count', 'debug', 'dir', 'dirxml', 'error', 'exception', 'group', 'groupCollapsed', 'groupEnd', 'info', 'log', ...


4

SPFx uses a Gulp plugin called Gulp connect to start the webserver hosting the Workbench. You're right saying that Gulp is a task-runner. In a way you could compare it MSBuild in .NET development. Also your comparison of Node to CLR is correct in the context of SPFx.


4

I assume you have installed Node, Gulp and Yeoman without errors. I also assume you have created a new SPFx project using the command yo @microsoft/sharepoint When done you navigate to the root folder of your project (if not already there) and type gulp serve I've made many mistakes typing server instead of serve, so pay attention to the correct command. ...


4

Issue was with the existance of the web server. Solution: Go to gulp location within your solution and use below..Solved! $ npm install --save-dev gulp-webserver This would be usefull..npmjs-gulpserver


4

install the latest version of node install the latest version of npm: npm i -g npm@next run the following in your cmd window or commander window: call npm uninstall -g chalk call npm uninstall -g loadash call npm uninstall -g tar-fs call npm uninstall -g update-notifier call npm uninstall -g yeoman-generator call npm uninstall -g yosay call npm uninstall -g ...


4

As Wictor mentions, you need a developer tenant. It sounds like there are some issues people are facing though. While we are sorting out the issue, does the following tenant sign up work? https://portal.microsoftonline.com/Signup/MainSignUp.aspx?OfferId=6881A1CB-F4EB-4db3-9F18-388898DAF510&DL=DEVELOPERPACK That should give you a 30 day trial ...


4

I had the same issue when I couldn't install Phantom due to an error on their server. I fixed the issue by rerunning npm i in the command line.


4

You don't seem to have any markup returned from your render method. In your JSX (or in this case TSX) markup you just need to add the onclick and point to a function in your class, something like this: import * as React from 'react'; import { IHelloWorldWebPartProps } from '../IHelloWorldWebPartProps'; export interface IHelloWorldProps extends ...


4

I just ran into the same problem, and fixed it by running the gulp --ship command after I changed the "write-manifests.json" file. (The tutorial at HelloWorld, Deploy to CDN does not run that command after changing the "write-manifests.json" file)


4

There is a sample for Taxonomy in sp-dev-fx-webparts. Following things you can get from this sample Reading taxonomy term stores' hierarchy from SharePoint Loading JavaScript Object Model scripts creating Knockout components I believe you can get help from this file to get term Termset.


Only top voted, non community-wiki answers of a minimum length are eligible