SpFx Helloworld webpart does not show up under modern Page toolbox
Expected or Desired Behavior Upon installation of the app, i can add the webpart to the pages as well Observed Behavior After adding app ,i try to add the app to my page, the app is not showing up in the list of the available apps. Steps to reproduce Follow the steps mention in https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/build-a-hello-world-web-part and created simple helloworld web part Add the .sppkg file in appcatalog and add the app in site Expected behavior After adding app in site, I should able to add the web part on page. Environment details I have two tenants, on test tenant I don't face any issue it is working perfectly fine. But on Production tenant I am facing this issue Your Developer Environment: - Windows 10 Target Environment: SharePoint Online Framework: Node.js v10 Browser(s): Chrome v79 Tooling: VS Code Additional context I am trying to add Modern Script Editor web part from https://medium.com/niftit-sharepoint-blog/add-the-script-editor-webpart-back-to-sharepoint-modern-experience-688a7b7208e4blog but I cant add it on production as I can not see it in web part list after deployment,so I am trying to deploy the simple Helloworld WebPart but I cannot see it as well in web part list on Production Tenant. On Test tenant everything is working fine. Note : I have admin account with admin access. In Past I have deployed SPFX Extension and it worked very well Thanks for your contribution! Sharing is caring.
Rules in config/tslint.json file of SPFx scaffolding are being ignored.
I ran the current Yeoman SharePoint generator, and got the following ts-lint file in the config directory (with a few minor tweaks added). From what I can tell the trailing-comma rule should be disabled (it's set to false), but it's not. I'm still getting red squigglies when I don't have a trailing comma (see below). That's just one example of a number of tslint scaffolding rules that appear to be ignored. What am I missing? Thanks! :-) (I have also posted https://sharepoint.stackexchange.com/questions/235288/how-do-i-disable-trailing-comma-tslint-rule-in-spfx-scaffolding.) "$schema": "https://dev.office.com/json-schemas/core-build/tslint.schema.json", // Display errors as warnings "displayAsWarning": true, // The TSLint task may have been configured with several custom lint rules // before this config file is read (for example lint rules from the tslint-microsoft-contrib // project). If true, this flag will deactivate any of these rules. "removeExistingRules": true, // When true, the TSLint task is configured with some default TSLint "rules.": "useDefaultConfigAsBase": false, // Since removeExistingRules=true and useDefaultConfigAsBase=false, there will be no lint rules // which are active, other than the list of rules below. "lintConfig": { // Opt-in to Lint rules which help to eliminate bugs in JavaScript "rules": { "class-name": false, "export-name": false, "forin": false, "label-position": false, "member-access": true, "no-arg": false, "no-console": false, "no-construct": false, // "no-duplicate-switch-case": true, "no-duplicate-variable": true, "no-eval": false, "no-function-expression": true, "no-internal-module": true, "no-shadowed-variable": true, "no-switch-case-fall-through": true, "no-unnecessary-semicolons": true, "no-unused-expression": true, "no-use-before-declare": true, "no-with-statement": true, "semicolon": true, "trailing-comma": false, "typedef": false, "typedef-whitespace": false, "use-named-parameter": true, "typeof-compare": true, "variable-name": false, "whitespace": false } } }Cross-domain request in SPFx
How can I make a cross-domain request in a Client Side Web Part built with the SharePoint Framework? My need is to access SharePoint 2016 data from a SharePoint 2016 site in another domain (same credentials). I found a crossDomainWeb method in the documentation for the add-in model, but nothing for SPFx.
SPFX 18.2 gulp serve issues
I have recently updated a number of modern spfx webparts to spfx 18.2 and this morning when I try to debug in workbench (locally and on tenant) I am getting serve errors in relation to react and react-dom I am able to serve projects not using react successfully but when using spfx 18.2 but not react 16.8.4 - has anybody else encountered this issue. I have restored to previous code backup, as well as restoring to previous days last git commit neither had a positive effect. I get no errors in terminal but workbench shows the following message: SPLoaderError.loadComponentError]: ***Failed to load component "174429f3-8ff8-4143-8f12-7c398d264e9a" (FusionWebPartWebPart). Original error: ***Failed to load URL 'https://localhost:4321/node_modules/react/dist/react.js' for resource 'react' in component '174429f3-8ff8-4143-8f12-7c398d264e9a' (FusionWebPartWebPart). The file was not found in the server. Make sure that you are running 'gulp serve'. ***INNERERROR: ***Failed to load URL 'https://localhost:4321/node_modules/react/dist/react.js' for resource 'react' in component '174429f3-8ff8-4143-8f12-7c398d264e9a' (FusionWebPartWebPart). The file was not found in the server. Make sure that you are running 'gulp serve'. ***CALLSTACK: Error at SPLoaderError.SPError [as constructor] (https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js:8390:24) at new SPLoaderError (https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js:4036:28) at Function.ErrorBuilder.buildErrorWithVerboseLog (https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js:3789:21) at Function.ErrorBuilder.buildLoadComponentError (https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js:3697:21) at https://localhost:4321/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js:6275:47 Vesa Juvonen
