Skip to main content
3 votes

Workbench issues with spfx 18.2 and react 16.8.4

Insert 2 lines to your gulpfile.js 'use strict'; const path = require('path'); const gulp = require('gulp'); const build = require('@microsoft/sp-build-web'); build.addSuppression(`Warning - [sass] ...
WondeRu's user avatar
  • 31
3 votes
Accepted

webpack "Module not found: Error: Cannot resolve 'file' or 'directory"

There are issues for two specific scenarios in this issue, so let's tackle them one-by-one. First would recommend ensuring that you have the latest version of the Yeoman templates by executing npm ...
Vesa Juvonen's user avatar
2 votes

Reactjs, TypeScript & Webpack on SharePoint2013

As Vipul Kelkar mentioned in his 2nd paragraph, you can perfectly use that development stack with SharePoint 2013. You can use whatever front-end framework you like. However, you cannot use the SPFx ...
Oak3's user avatar
  • 1,615
1 vote
Accepted

I can't make external component library work on SPFX

Ok... I figure out the error. on my externals I need to refer to react as in: externals: { 'react': 'react', } Also import react in every component that uses it. now it works and uses the current ...
Ricardo Silva's user avatar
1 vote

NPM packages for React webpart SharePoint Online try to access 'fs' on client side but it's not even necessary? React SPFX

I managed to fix this error by adding the following to the gulpfile.js: build.configureWebpack.mergeConfig({ additionalConfiguration: (generatedConfiguration) => { generatedConfiguration.node ...
Rodelyo Pakundo's user avatar
1 vote

NPM packages for React webpart SharePoint Online try to access 'fs' on client side but it's not even necessary? React SPFX

You are not able to modify the actual webpack configuration file that is provided ootb by the spfx tools. But they have made it possible to add your own loaders. Take a look at this post by the spfx ...
Johan Brännmar's user avatar
1 vote

Workbench issues with spfx 18.2 and react 16.8.4

I guess the best thing to start is gulp clean Then gulp build and then gulp serve. Maybe these simple steps will help you to refresh all dependencies and get rid of outdated artifacts
MP_89's user avatar
  • 149
1 vote
Accepted

Reactjs, TypeScript & Webpack on SharePoint2013

SharePoint framework works only on SharePoint online and SharePoint 2016 on-premise : https://docs.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview Having said that, you can ...
Vipul Kelkar's user avatar
  • 1,534
1 vote
Accepted

Problems Unit Testing in SharePoint Framework (SPFx) with External Dependencies

you can add the jsChart to the devDependencies in package.json and also keep it in the external dependency configuration. Doing that the tests will run and in the same time the jsChart would not be ...
Velin's user avatar
  • 251
1 vote
Accepted

SharePoint Framework: Module not loaded correctly when pressing F5 in IE

This solution solves the problem for me: remove everything regarding jquery and "jquery.typeahead" from config.json require "jquery.typehead" from "node_modules" directly The require looks like this:...
Heinrich Ulbricht's user avatar
1 vote

SharePoint Framework: Module not loaded correctly when pressing F5 in IE

Here's what I got from a member of the team when I posed this to them: One thing that surprises me is that he is putting both dependencies as ‘jQuery’ global name, which is confusing, and looks like ...
PatMill_MSFT's user avatar
  • 2,466

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