Giter Site home page Giter Site logo

sp-dev-solutions's Introduction

page_type products languages extensions
sample
office-sp
typescript
contentType createdDate
samples
12/13/2022 12:47:19 PM

Microsoft 365 Platform Community Solutions

Welcome to the Microsoft 365 Platform Community Solutions for SharePoint repository. This repository contains samples and templates you can use as foundations and patterns of solutions related on the SharePoint technologies.

STATUS

These web parts are currently in preview, and undergoing further updates to improve quality and add capabilities, based on your feedback.

About

This repository contains solution samples that implement different user scenarios that you can use as part of your own solutions within SharePoint sites. These samples end-to-end solutions that contain all of the components you need to fulfill productivity needs of users and teams. For developers, these are extended examples, and contain some modules and patterns you may find useful to re-use in your solutions.

We welcome your reported issues, pull requests, and new solution samples. Please use the Github issues list to submit your feature requests and issues, and please submit pull requests and bug fixes. For new solutions, you will want to review the solutions standards criteria for inclusion. For more information, see Contribution Guidance.

Solution Samples

Solution Description Link
ChangeRequests Manage and close change requests opened by users. Link
Column Formatter Easy editor for modern listview Column Formatting Link
ContactManagement Organize and manage contacts and organizations. Link
LinksAndHandlebarsTemplate Different kinds of visuals for hosting sets of links on a page, including with custom Handlebars Templates Link
Multilingual Pages Solution to create, manage, and consume multilingual pages based on users preferred language. Link
Pages API Solution to using Pages API to get/create/update/delete SharePoint Pages. Link
InventoryCheckOut Manage a list of items in an inventory, and let users check out and reserve items. Link
Site Designs Studio Enables the management of Site Designs and Site Scripts directly in the browser Link
TimeAway Provides a simple out-of-office tracker for members of your team. Link
ModernSearch User friendly search experience in the modern SharePoint interface Link
ModernSearchRenderers Custom renderers for the ModernSearch solution. Link

Additional resources

Using the solutions

To build and start using these projects, you'll need to clone and build the projects.

Clone this repository by executing the following command in your console:

git clone https://github.com/pnp/sp-dev-solutions.git

Navigate to the cloned repository folder which should be the same as the repository name:

cd sp-dev-solutions

To access the solutions use the following command, where you replace solution-folder-name with the name of the solution you want to access.

cd solution-folder-name

Now run the following command to install the npm packages:

npm install

This will install the required npm packages and dependencies to build and run the client-side project.

Once the npm packages are installed, run the following command to preview your web parts in SharePoint Workbench:

gulp serve

Contributions

These solutions are direct from the feature teams, Microsoft 365 Platform Community core team (http://aka.ms/m365/community) or shared by the community. This project's contributors include Microsoft and community contributors. Work is done as as open source community project. We welcome your input on issues and suggestions for new samples. We also welcome community contributions around new solutions.

Please have a look on our Contribution Guidance before submitting your pull requests, so that we can get your contribution processed as fast as possible. Thanks!

Sharing is caring!

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.

sp-dev-solutions's People

Contributors

aboredman avatar appieschot avatar bschlintz avatar dependabot[bot] avatar eoverfield avatar franckyc avatar heinrich-ulbricht avatar hugoabernier avatar itsknob avatar jdonajkowski avatar johnguy0 avatar juliemturner avatar mammerla avatar mptolly avatar nokafor avatar paolopia avatar ryanmcdonough avatar sangle7 avatar spshire avatar stijnbrouwers avatar taraldga avatar tdwhite0 avatar thechriskent avatar theresaeller avatar thomyg avatar vesajuvonen avatar waldekmastykarz avatar wobba avatar yannickre avatar ypcode avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

sp-dev-solutions's Issues

Guidance on working with custom Monaco build

Category

  • Question
  • Bug
  • Enhancement

First, thank you for hosting this repo. It is an awesome resource.

I stumbled across this repo while trying to integrate the Monaco editor into an SPFx webpart. After lots of spinning, I found @thechriskent had successfully done it using a custom build.

This is great, however one unfortunate side effect of the implementation is that the bundle includes the full Monaco build and is around 10MB.

This isn't a big deal for "Admin" tools like Column Formatter and Site Design Studio. In my scenario however I would only need to load the Monaco Editor when the user is in the Web Part Property Panel.

I'd prefer not to force all users to download a 10 MB webpart bundle when 99% of that is only needed for Edit mode.

Is there a way I can put the custom Monaco build in its own bundle or as its own "component", then piggyback on some native SP module loading utilities to pull it in ONLY when the page is in edit mode?

Worst case, would this work? Is there a more SPFx'y way to do it?

  1. Host the custom build in Blob storage
  2. Continue to register monaco as an external in config.json
  3. Add logic to the MonacoEditor.tsx component to load the externally hosted file before initializing the editor(check global to see if it's already on the page too).

Hub Links Web Part loading issue

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

Web part loads every time a page is loaded

Observed Behavior

Web Part intermittently gets stuck in the pre-load when a modern page is rendered in SPO.
image

Steps to Reproduce

This has happened when adding the web part to a modern page. Sometimes I can get the web part added to the page and configured but then it also happens later when visiting the page.

I have not been able to identify any errors for this. If anyone knows of a way to troubleshoot this I would be happy to try that on my site. Based on the intermittent basis of this issue it may be hard to reproduce on other tenants.

Argument of Type - Service Scope & Service Key

nodecmddetails.txt
packagedetails.txt
package-lock.json details.txt

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

Sharepoint workbench to load

Observed Behavior

I receive the following errors:
[10:37:58] Error - typescript - src\webparts\siteDesignsStudio\services\apps\AppsService.ts(14,39): error TS2345: Argument of type 'ServiceScope' is not assignable to parameter of type 'ServiceScope'.
[10:37:58] Error - typescript - src\webparts\siteDesignsStudio\services\hubSites\HubSitesService.ts(14,39): error TS2345: Argument of type 'ServiceScope' is not assignable to parameter of type 'ServiceScope'.
[10:37:58] Error - typescript - src\webparts\siteDesignsStudio\services\lists\ListsService.ts(130,39): error TS2345: Argument of type 'ServiceScope' is not assignable to parameter of type 'ServiceScope'.
[10:37:58] Error - typescript - src\webparts\siteDesignsStudio\services\siteDesigns\SiteDesignsService.ts(22,39): error TS2345: Argument of type 'ServiceScope' is not assignable to parameter of type 'ServiceScope'.
[10:37:58] Error - typescript - src\webparts\siteDesignsStudio\services\siteScriptSchema\SiteScriptSchemaService.ts(291,62): error TS2345: Argument of type 'ServiceKey' is not assignable to parameter of type 'ServiceKey'.
[10:37:58] Error - typescript - src\webparts\siteDesignsStudio\services\siteScriptSchema\SiteScriptSchemaService.ts(294,58): error TS2345: Argument of type 'ServiceKey' is not assignable to parameter of type 'ServiceKey'.
[10:37:58] Error - typescript - src\webparts\siteDesignsStudio\services\themes\ThemesService.ts(14,39): error TS2345: Argument of type 'ServiceScope' is not assignable to parameter of type 'ServiceScope'.
[10:37:59] Error - 'typescript' sub task errored after 7.62 s

Steps to Reproduce

google chrome
npm install
gulp serve

Steps Already Tried
reinstall npm modules
trust-dev-cert

I am new to this so please help :)

Applying JSON Properties to Search Box / Search Refiner WebParts problem

Category

  • Question
  • Bug
  • Enhancement

Hi Folks,

Am working on a mechanism to deploy using PNP the search refiner webpart with the search box based on its web properties to another site. This is to ensure that the configuration can be replicated programmatically, without having to manually re-enter all the settings for the search refiner and search box.

To do this, I extracted the PropertiesJSON from the Search Box and the Search Results with Refiners on an existing page using Get-PnPClientSideComponent.

Then, I recreated the page on another site, added the Search Box and Search Results with Refiners webparts and applied the JSON using Set-PnPClientSideWebPart.

I've run into some problems:
1: The web parts cannot be configured; the configuration panel will not display.
2: If the page is Saved as Draft, a serialization error is displayed. Also, the Search Refiner is not keeping its state; the data source is not being set dispite that having entries in the JSON. Am guessing this is because the JSON included the ID of Search Box it was connected to, which will be different for Search Box on the new page...

Steps to Reproduce

1: Create a new site page called Home;
2: Add the Search Box and Search Refiners web part onto the Home page;
3: Using Get-PnPClientSideComponent, extract the JSON for both web parts;
4: On a new site, create the site page called Home.
5: Add the Search Box and Search Refiners web part onto this Home page;
6: Using Set-PnPClientSideWebPart, set the PropertiesJSON property to the JSON extracted in step 3 above.

Can anyone please advise what the best method would be to apply JSON obtained from these webparts to the same placed webparts on a different page?

ModernSearch (react-search-refiners package) web-part package doesn't have refiner, paging and search navigation webaprt included.

Category

  • Question

Expected or Desired Behavior

As described in the PnP blog video and description in ModernSearch web-part has refiner, paging and search navigation included. I was using a older version and pulled the latest, I don't see those in my web-part inventory.

Observed Behavior

ModernSearch web-part package doesn't have refiner, paging and search navigation included. I was using a older version and pulled the latest, I don't see those in my web-part inventory.

If possible, please put the details about, how to get Search refiners, Search Navigation, Search paging web-part.

Modern search refinable result open document in client application

Category

  • Question
  • Bug
  • Enhancement

Is there a way to open documents in the client application from the resultwebpart? Or how do I tell SharePoint to open the document in the client application instead of office online? Is there a parameter to the page _layouts/15/Doc.aspx like openInWeb=false or some other simple solution?

I have configured the library to open documents in client application and enabled the feature Open documents in client application by default.

When I click on documents in the library it opens in the client but not from search. Both from a old classic searchcenter and the refinable result webpart it opens in office online.

[ModernSearch] Search Refiner Web Part doesn't reset on new query

Category

  • Bug

Expected or Desired Behavior

I do a search query (v3.0.0.0), then apply a refiner with the Search Refiners Web Part and then do a new search query, I expect the refiners to be reset.

Observed Behavior

The refiners stay applied on the new search query.

Steps to Reproduce

RefinerWebPartProblem

@FranckyC : I believe this was introduced with the refactoring (it was working in my pull request), any idea how to fix?

Pnp search not showing MS Teams data

Category

  • Bug

Expected or Desired Behavior

The Pnp Search result spfx web-part should show result from MS Teams as there is no change in result resource. If you try default modern search, in organization search result page the document appears.

Observed Behavior

The Pnp Search result spfx web-part doesn't show result from MS Teams. If you try with same key word/text in OOTB modern search, in organization search result tab of the page, the document appears but it doesn't appear in PnP search result web-part.

Steps to Reproduce

1- Create a Teams in MS teams. It will create SharePoint site.
2- Upload a document.
3- Create a modern Communication site. Configure PnP search box and Search result web-part.
4- Try searching for the document uploaded to MS Teams. It doesn't appear.

[GlobalFooter] footer doesn't stay at bottom on SharePoint App

Category

  • Question
  • [X ] Bug
  • Enhancement

Expected or Desired Behavior

Footer to stay on bottom of the page

Observed Behavior

Scrolling the pages makes the Global Footer move up SOMETIMES

Steps to Reproduce

  1. Go to Modern page on SharePoint Mobile App (android)
  2. Scroll down
  3. See the footer go up (in some cases, not all)

Unable to serve TimeAway

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • Question
  • [x ] Bug
  • Enhancement

Expected or Desired Behavior

Tried to run npm install and gulp serve within the TimeAway solution directory

Observed Behavior

Several dependency issues appeared on the first gulp serve.
Attempted to resolve the unknown module reference in the error output, which reduced it but then these were replaced with several typescript errors.

PS C:\AppDev\sp-dev-solutions\solutions\TimeAway> gulp serve Build target: DEBUG [14:38:55] Using gulpfile C:\AppDev\sp-dev-solutions\solutions\TimeAway\gulpfile.js [14:38:55] Starting gulp [14:38:55] Starting 'serve'... [14:38:55] Starting subtask 'configure-sp-build-rig'... [14:38:55] Finished subtask 'configure-sp-build-rig' after 4.45 ms [14:38:55] Starting subtask 'spfx-serve'... [14:38:55] Starting server... [14:38:55] Error - [spfx-serve] The api entry could not be loaded: node_modules/@microsoft/sp-webpart-workbench/lib/api/ [14:38:55] Finished subtask 'spfx-serve' after 244 ms [14:38:56] Starting subtask 'pre-copy'... [14:38:56] Finished subtask 'pre-copy' after 11 ms [14:38:56] Starting subtask 'copy-static-assets'... [14:38:56] Starting subtask 'sass'... [14:38:56] Server started https://localhost:4321 [14:38:56] LiveReload started on port 35729 [14:38:56] Running server [14:38:56] Opening https://localhost:5432/workbench using the default OS app [14:38:57] Finished subtask 'copy-static-assets' after 1 s [14:38:57] Finished subtask 'sass' after 1.01 s [14:38:57] Starting subtask 'tslint'... [14:38:58] Starting subtask 'typescript'... [14:38:58] [typescript] TypeScript version: 2.4.2

After this, several typescript errors are shown.

`Could not find implementations for the following rules specified in the configuration:
no-unused-imports
Try upgrading TSLint and/or ensuring that you have all necessary custom rules installed.
If TSLint was recently upgraded, you may have old rules configured which need to be cleaned up.

Warning: no-duplicate-case rule is deprecated. Replace your usage with the TSLint no-duplicate-switch-case rule.
Warning: valid-typeof rule is deprecated. Replace your usage with the TSLint typeof-compare rule.
[14:39:00] Error - typescript - unknown filename(0,0): error TS2688: Cannot find type definition file for 'es6-collections'.
[14:39:02] Error - typescript - node_modules@microsoft\sp-http\dist\index-internal.d.ts(180,22): error TS2420: Class 'HttpClientResponse' incorrectly implements interface 'Response'.
[14:39:02] Error - typescript - node_modules@microsoft\sp-page-context\dist\index-internal.d.ts(134,23): error TS2304: Cannot find name 'AzureActiveDirectoryInfo'.
[14:39:02] Error - typescript - node_modules@microsoft\sp-page-context\dist\index-internal.d.ts(536,21): error TS2304: Cannot find name 'O365GroupAssociation'.
[14:39:02] Error - typescript - node_modules\immutability-helper\index.d.ts(12,9): error TS2304: Cannot find name 'ReadonlySet'.
[14:39:02] Error - typescript - node_modules\immutability-helper\index.d.ts(14,4): error TS2304: Cannot find name 'ReadonlySet'.
[14:39:02] Error - typescript - node_modules\immutability-helper\index.d.ts(17,9): error TS2304: Cannot find name 'ReadonlyMap'.
[14:39:02] Error - typescript - node_modules\immutability-helper\index.d.ts(19,4): error TS2304: Cannot find name 'ReadonlyMap'.
[14:39:02] Error - typescript - src\libraries\components\Container\MyTimeAwayContainer.tsx(93,19): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\Container\MyTimeAwayContainer.tsx(99,23): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(44,7): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(131,7): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(143,7): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(155,7): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(179,19): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(190,21): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(208,19): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(218,27): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\CreateDialog\TimeAwayCreateDialog.tsx(234,7): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\libraries\components\ListItem\MyTimeAwayListItem.tsx(49,15): error TS2339: Property 'icon' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes & Readonly<{ children?: ReactNode; }> & Re...'.
[14:39:02] Error - typescript - src\libraries\components\ListItem\MyTimeAwayListItem.tsx(54,15): error TS2339: Property 'icon' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes & Readonly<{ children?: ReactNode; }> & Re...'.
[14:39:02] Error - typescript - src\libraries\dataProviders\SharePointDataProvider.ts(3,3): error TS2305: Module '"C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/@microsoft/sp-http/dist/index-internal"' has no exported member 'SPHttpClientBatch'.
[14:39:02] Error - typescript - src\libraries\dataProviders\SharePointDataProvider.ts(52,76): error TS2339: Property 'beginBatch' does not exist on type
'SPHttpClient'.
[14:39:02] Error - typescript - src\libraries\dataProviders\SharePointDataProvider.ts(65,76): error TS2339: Property 'beginBatch' does not exist on type
'SPHttpClient'.
[14:39:02] Error - typescript - src\libraries\dataProviders\SharePointDataProvider.ts(78,76): error TS2339: Property 'beginBatch' does not exist on type
'SPHttpClient'.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\components\Container\TimeAwaySummaryContainer.tsx(38,19): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\components\Container\TimeAwaySummaryContainer.tsx(116,19): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\components\Container\TimeAwaySummaryContainer.tsx(123,19): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\components\Container\TimeAwaySummaryContainer.tsx(128,21): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\components\list\TimeAwaySummaryList.tsx(60,23): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'typeof "C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/immutability-helper/index"' has no compatible call signatures.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\dataProviders\TimeAwaySummaryDataProvider.ts(9,3): error TS2305: Module '"C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/@microsoft/sp-http/dist/index-internal"' has no exported member 'SPHttpClientBatch'.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\dataProviders\TimeAwaySummaryDataProvider.ts(11,3): error TS2305: Module '"C:/AppDev/sp-dev-solutions/solutions/TimeAway/node_modules/@microsoft/sp-http/dist/index-internal"' has no exported member 'ISPHttpClientBatchCreationOptions'.
[14:39:02] Error - typescript - src\webparts\timeAwaySummary\dataProviders\TimeAwaySummaryDataProvider.ts(44,53): error TS2339: Property 'beginBatch' does not exist on type 'SPHttpClient'.
[14:39:02] Finished subtask 'tslint' after 5.84 s
[14:39:03] Error - 'typescript' sub task errored after 4.46 s
TypeScript error(s) occurred.
[14:39:38] Server stopped
About to exit with code: 0
Process terminated before summary could be written, possible error in async code not continuing!`

Steps to Reproduce

  1. Clean environment
  2. Pull repo
  3. cd to TimeAway solutions directory. Run npm install and gulp serve as directed in the README.

react-search-refiners handlebar helper getDate not working consistently

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

Handlebar template using a handlebar helper {{getDate Created "D MMMM"}} to display a date from a SharePoint date field consistently.

Observed Behavior

The template displays a date correctly, but in every 5-10 page load, the date is not being displayed at all when {{getDate Created "D MMMM"}} helper is used. No errors in the browser are logged.
If I output just {{Created}}, this date will always display eg:
First output is using {getDate Created "D MMMM"}}, second {{Created}}

Start Date:
Start Date: 2019-03-04T00:00:00Z

Steps to Reproduce

I'm using react-search-refiners 2.5.1.0 & 3.0.0.0 with "skipFeatureDeployment": true, SharePoint Online.

Create a list and create few list items, then create a simple search results template and output the information:

<div><div>Created Date:</div><div>{{getDate Created "D MMMM"}}</div></div>
<div><div>Created Date:</div><div>{{Created}}</div></div>

Refresh browser few times, the date doesn't from time to time. Chrome and IE have been tested with the same result. The out of the box default template is also showing this behavior.

LeadsLOBSolution is not working on the microsoft teams desktop version

Hi guys,

I have installed the 'LeadsLOBSolution' on my tenant. This app is working fine on the Microsoft teams web version but not working on the desktop version. Is this a know issue?

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

The leads tab should be displaying all the demo leads

Observed Behavior

When i go to the leads tab its keep showing loading icon.
image

Steps to Reproduce

  1. get the latest from the github
  2. run npm i
  3. run gulp build
  4. run gulp bundle --ship
  5. run gulp package-solution --ship
  6. copy the zip file from the teams folder to the teams
  7. add the leads app to the desired team channel
  8. view the tab

Thank you

[ModernSearch] Cannot Find module "readline"

Category

  • Question
  • [ X] Bug
  • Enhancement

Expected or Desired Behavior

Added the Search Box, Search Filters and Search Results webpart, using default settings.
When searching for a file on the current site collection, it should show the results.

Observed Behavior

Getting an error:
[SharePointDataProvider.search()]: Error: Error: Cannot find module "readline"
[SearchContainer._componentWillReceiveProps()]: Error: Error: Cannot find module "readline"
Failed to load resource: the server responded with a status of 403 (All records were throttled.)

Steps to Reproduce

Adding the modern search latest version to a modern sharepoint home.aspx

[ModernSearch] Roadmap & enhancements

Category

  • Enhancement

Expected or Desired Behavior

Possible enhancements for the ModerSearch solution:

Search box

  • Clear hashtags from the URL if present when a new query is entered

Search refiners

  • Add a 'Show more' + search box options for long refiners list
  • Add an horizontal layout with dropdown
  • Add shimmers for the initial load. Not a big deal but it can be weird on the first query.
  • Add predefined refiner templates (alphabetical filter, taxonomy picker).
  • Add an option to display managed metadata full path #155

Search navigation

  • Allow predefined queries on tabs to enable single search page scenario with query rules and result types.
  • Datasource selection limited to Search Results web part
  • Fix issue where it doesn't correctly identify the homepage as being part of the navigation collection, thus not marking any link as active

Search results

  • Retrieve context parameters (hashtags, query string parameters) when a default query is set.
  • Search usage analyics using App Insights
  • Explore Microsoft adaptive cards as a complement for templating. Waiting data binding feature

Please let us know before starting any of these feature so we can discuss the approach. #70

How to use Query String Parameters with Search Result WebPart

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • [X ] Question
  • Bug
  • Enhancement

Expected or Desired Behavior

I would like to use a URL querystring parameter in the search result web part but not sure how to do it.

In the first screen It is configured to use the page environment, querystring and my URL parameter is selected.

In my page URL I have ?ListItemId=1. So how do I use this querystring parameter?
I'v been trying in my search request: ListItemId={QueryString.ListItemId} but it does not work.
I know that ListeItemId=1 is working.

Thanks!

caml.js link 404

Greetings. Just wanted to let you know that the caml.js links noted in readme files may need to be updated.

Category

  • [*] Bug

Observed Behavior

caml.js links in README.md result in 404.

react-search-refiners - Filter Panel too big for mobile app & mobile browser

Category

  • Question
  • Bug
  • Enhancement

Authors

@FranckyC & @wobba

Expected or Desired Behavior

The filter panel of react-search-refiners WebPart should be fully visible on browser and SharePoint mobile app and not depend of the screen resolution.

Observed Behavior

The filter panel is too big for mobile screen and it is troncated.

Steps to Reproduce

WebPart react-search-refiners v.2.4.0.1 - master

Using the SharePoint mobile app or a mobile browser, open the filter panel of the WebPart.

Submission Guidelines

Hi,
This bug seems to be linked to the use of type={PanelType.custom} and customWidth="450px" for this Panel in FilterPanel.tsx.
By replacing type={PanelType.custom} with type={PanelType.medium} and removing customWidth="450px" seems to solve it but i wanted to know if this choice of type was done to resolve another bug or issue.
Have a nice day :-)

Thanks for your contribution! Sharing is caring.

Search Refiners with Term Store Values

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • Question
  • [] Bug
  • Enhancement

Expected or Desired Behavior

When configuring a refiner from 'RefinableString02', for example - which - is a field from a TAXONOMY (termstore) field - the refiner display should show as ;

Finance (2)

Observed Behavior

Instead, it shows with the full GUID - for the field value ;
4;#Finance|919f07ce-89cd-456e-97da-073d99cb1863 (2)

** It works, and refines the results - but - the display value isn't pretty

Steps to Reproduce

  1. Create site column - based on a termstore value
  2. Add to SP Doc Lib
  3. Include documents, and set properties
  4. Set Search Schema - eg. RefinableString02 - and add the crawled property
  5. WIthin webpart setting - include the field - as a refiner

Global Footer Command Bar collapses in libraries and lists

Category

  • [x ] Question
  • [x ] Bug
  • Enhancement

Expected or Desired Behavior

We recently installed the global footer solution provided within this repo and are pretty happy with it as it is. Our expectation was, that it shows up on every element in every modern team site or communication site depending on the available space.

Observed Behavior

Recently we noticed that the desired behavior is achieved on every page in modern sites. But, as soon as you switch into a library or list, the command bar collapses into a small menu, although the screen size did not change.
see screenshots for reference.

As the code for this is pretty simple, it seems that this is a bug within the command bar control from fabric ui. Maybe anyone can confirm this, or give a hint on how to fix it.

On page:
image

In library
image

Steps to Reproduce

  1. install the solution
  2. check that it is displayed on modern sites
  3. switch to "Documents" library on the site
  4. check footer again.

[ModernSearch] [WIP] Allow refiners to be displayed in their own web part

  • Enhancement

Feature enhancement

Just a FYI to let you know I'm working on a feature to (if wanted) show to Refiners in their own web part instead of in the main web part as a sliding panel. I took great care in making sure that both methods would still work.

I know that it's not really the modern look and feel, but a lot of customers are still asking for a similar experience as with the Enterprise Search Center.

Development status

  • Run as a separate web part, data connections flowing in both ways
  • Display spinner/loading animation on Refiners web part when reiner selected
  • Test with PnP provisioning making sure it's possible to provision a Search Center
  • Add readme

Branch

If you want to follow along => https://github.com/YannickRe/sp-dev-solutions/tree/feature/searchRefiners

Gulp Serve error

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • [x ] Question
  • [x ] Bug
  • Enhancement

Expected or Desired Behavior

After running 'gulp serve' the expected behavior is for the local workbench to open with option to add and configure the webparts.

Observed Behavior

The observed behavior is a blank webpage and no options to add the webparts.

Steps to Reproduce

AM I doing something wrong? This is what I did. I cloned the repo, then moved the Modern Search solution to a new folder on my computer. I ran NPM install, then gulp serve. The build starts, a webpage opens, then the build fails with exit code 2. Here is the output after running gulp serve:
PS C:\SPFxProjects\ModernSearch\react-search-refiners\spfx> gulp serve
Build target: DEBUG
[11:52:17] Using gulpfile C:\SPFxProjects\ModernSearch\react-search-refiners\spfx\gulpfile.js
[11:52:17] Starting gulp
[11:52:17] Starting 'serve'...
[11:52:17] Starting subtask 'configure-sp-build-rig'...
[11:52:17] Finished subtask 'configure-sp-build-rig' after 22 ms
[11:52:17] Starting subtask 'spfx-serve'...
[11:52:18] Starting server...
Starting api server on port 5432.
Registring api: /workbench
Registring api: /
[11:52:18] Finished subtask 'spfx-serve' after 1.16 s
[11:52:19] Starting subtask 'pre-copy'...
[11:52:19] Finished subtask 'pre-copy' after 461 ms
[11:52:19] Starting subtask 'copy-static-assets'...
[11:52:19] Starting subtask 'sass'...
[11:52:19] Server started https://localhost:4321
[11:52:19] LiveReload started on port 35729
[11:52:19] Running server
[11:52:19] Opening https://localhost:5432/workbench using the default OS app
Request: [::1] '/workbench'
Request: '/temp/workbench.html'
Request: '/temp/manifests.js'
Request: '/temp/workbench-packages/@microsoft_sp-loader/dist/sp-loader-assembly_default.js'
Request: '/temp/workbench-packages/@microsoft_sp-webpart-workbench/lib/api/workbenchInit.js'
[11:52:22] Finished subtask 'copy-static-assets' after 2.8 s
[11:52:23] Finished subtask 'sass' after 4.19 s
[11:52:23] Starting subtask 'tslint'...
[11:52:23] [tslint] tslint version: 5.9.1
[11:52:24] Starting subtask 'tsc'...
[11:52:24] [tsc] typescript version: 2.4.2
[11:52:36] Finished subtask 'tslint' after 13 s
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(96,42): error TS2339: Property 'filter' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'.
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(107,31): error TS2339: Property 'searchWp__filterPanel__body__group' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'.
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(132,44): error TS2339: Property 'searchWp__selectedFilters' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'.
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(147,64): error TS2551: Property 'searchWp__filterPanel__body' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'. Did you mean 'searchWp__sortPanel__body'?
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(149,70): error TS2339: Property 'searchWp__filterPanel__body__allFiltersToggle' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'.
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(158,60): error TS2551: Property 'searchWp__filterPanel__body' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'. Did you mean 'searchWp__sortPanel__body'?
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(197,36): error TS2339: Property 'searchWp__filterPanel__body__group__header' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'.
[11:52:37] Error - [tsc] src/webparts/searchResults/components/FilterPanel/FilterPanel.tsx(213,48): error TS2339: Property 'searchWp__filterPanel__body__headerIcon' does not exist on type '{ searchWp: string; searchWp__noresult: string; searchWp__buttonBar: string; searchWp__buttonBar_...'.
[11:52:37] Error - 'tsc' sub task errored after 13 s
exited with code 2

Donut

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

If you are reporting a bug, please describe the expected behavior. If you are suggesting an enhancement please describe thoroughly the enhancement, how it can be achieved, and expected benefit.

Observed Behavior

If you are reporting a bug, please describe the behavior you expected to occur when performing the action. If you are making a suggestion, you can delete this section.

Steps to Reproduce

If you are reporting a bug please describe the steps to reproduce the bug in sufficient detail to allow testing. Only way to fix things properly, is to have sufficient details to reproduce it. If you are making a suggestion, you can delete this section.

Submission Guidelines

Delete this section after reading

  • All suggestions or bugs are welcome, please let us know what's on your mind.
  • If you are reporting an issue around any of the samples, please ensure that you have clear reference on the sample and possibly code file, which should be fixed.
  • If you have technical questions about the framework, we’ll be monitoring #spfx, #spfx-webparts, and #spfx-tooling on (SharePoint StackExchange)[http://sharepoint.stackexchange.com/]. You can also alternatively submit your question to (SharePoint Developer group)[https://network.office.com/t5/SharePoint-Developer/bd-p/SharePointDev] at Office Network.
  • Remember to include sufficient details and context.
  • If you have multiple suggestions or bugs please submit them in separate bugs so we can track resolution.

Thanks for your contribution! Sharing is caring.

react-search-refiners: not working out of the box

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

Webpart works out the box

Observed Behavior

So this may just be my lack of knowledge, but I'm getting some issues with react-search-refiners out of the box. When I run gulp serve and load the webpart in the SharePoint workbench, it returns an error Cannot find module ".". I'm using Node v8.15.0

It also is spitting out the following error:
Warning - [webpack] 'dist': ./node_modules/log-utils/node_modules/ansi-colors/index.js 14:35-42 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted at CommonJsRequireContextDependency.getWarnings (<Path>\sp-dev-solutions\solutions\ModernSearch\react-search-refiners\spfx\node_modules\webpack\lib\dependencies\CommonJsRequireContextDependency.js:27:4) at Compilation.reportDependencyErrorsAndWarnings (<Path>\sp-dev-solutions\solutions\ModernSearch\react-search-refiners\spfx\node_modules\webpack\lib\Compilation.js:694:24) at Compilation.finish (<Path>\sp-dev-solutions\solutions\ModernSearch\react-search-refiners\spfx\node_modules\webpack\lib\Compilation.js:552:9) at applyPluginsParallel.err (<Path>\sp-dev-solutions\solutions\ModernSearch\react-search-refiners\spfx\node_modules\webpack\lib\Compiler.js:506:17) at <Path>\sp-dev-solutions\solutions\ModernSearch\react-search-refiners\spfx\node_modules\tapable\lib\Tapable.js:289:11 at _addModuleChain (<Path>\sp-dev-solutions\solutions\ModernSearch\react-search-refiners\spfx\node_modules\webpack\lib\Compilation.js:498:11) at processModuleDependencies.err (<Path>\sp-dev-solutions\solutions\ModernSearch\react-search-refiners\spfx\node_modules\webpack\lib\Compilation.js:468:14) at _combinedTickCallback (internal/process/next_tick.js:132:7) at process._tickCallback (internal/process/next_tick.js:181:9)

Steps to Reproduce

npm install
gulp serve
Use SharePoint workbench (not local)

Resize default file name column

Category

  • [*] Question

Hello, first of all thank you for your work.
Despite my documentation I can not resize (in width) the file name column (clickable). I use SharePoint Office 365 modern interface.

Thanks for your help.

Can't perform NPM INSTALL

Just downloaded the solution by using the instruction through GIT CLONE.

Tried to install the dependencies by calling NPM INSTALL and got the following error:

C:\DEV\sp-dev-solutions\solutions\ContactManagement>npm i
npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated [email protected]: not actively maintained anymore
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated @types/[email protected]: fetch types are now provided by '--lib dom'
npm WARN deprecated @types/[email protected]: This is a stub types definition for log4js (https://github.com/nomiddlename/log4js-node). log4js provides its own type definitions, so you don't need @types/log4js installed!
npm WARN deprecated @types/[email protected]: This is a stub types definition for chalk (https://github.com/chalk/chalk). chalk provides its own type definitions, so you don't need @types/chalk installed!
npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated [email protected]: connect 2.x series is deprecated
npm WARN deprecated [email protected]: This package is unmaintained. Use @sinonjs/formatio instead
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.

[email protected] install C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\deasync
node ./build.js

win32-x64-node-8 exists; testing
Binary is fine; exiting

[email protected] install C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

  export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

  npm config set proxy http://example.com:8080

[email protected] install C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\phantomjs-prebuilt
node install.js

PhantomJS not found on PATH
Download already available at C:\Users\user\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip
Verified checksum of previously downloaded file
Extracting zip contents
Removing C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\phantomjs-prebuilt\lib\phantom
Copying extracted folder C:\Users\user\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip-extract-1535946597025\phantomjs-2.1.1-windows -> C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\phantomjs-prebuilt\lib\phantom
Writing location.js file
Done. Phantomjs binary available at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\phantomjs-prebuilt\lib\phantom\bin\phantomjs.exe

@microsoft/[email protected] install C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules@microsoft\sp-loader
node npm-install-script.js

[email protected] postinstall C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-sass
node scripts/build.js

Building: C:\nodejs\node.exe C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\nodejs\node.exe',
gyp verb cli 'C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-gyp\bin\node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb which failed Error: not found: python2
gyp verb which failed at getNotFoundError (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:13:12)
gyp verb which failed at F (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:68:19)
gyp verb which failed at E (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:80:29)
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:89:16
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\index.js:42:5
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:152:21)
gyp verb which failed python2 { Error: not found: python2
gyp verb which failed at getNotFoundError (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:13:12)
gyp verb which failed at F (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:68:19)
gyp verb which failed at E (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:80:29)
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:89:16
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\index.js:42:5
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:152:21)
gyp verb which failed stack: 'Error: not found: python2\n at getNotFoundError (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:13:12)\n at F (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:68:19)\n at E (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:80:29)\n at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:89:16\n at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\index.js:42:5\n at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:152:21)',
gyp verb which failed code: 'ENOENT' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb which failed Error: not found: python
gyp verb which failed at getNotFoundError (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:13:12)
gyp verb which failed at F (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:68:19)
gyp verb which failed at E (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:80:29)
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:89:16
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\index.js:42:5
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:152:21)
gyp verb which failed python { Error: not found: python
gyp verb which failed at getNotFoundError (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:13:12)
gyp verb which failed at F (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:68:19)
gyp verb which failed at E (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:80:29)
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:89:16
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\index.js:42:5
gyp verb which failed at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\windows.js:36:5
gyp verb which failed at FSReqWrap.oncomplete (fs.js:152:21)
gyp verb which failed stack: 'Error: not found: python\n at getNotFoundError (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:13:12)\n at F (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:68:19)\n at E (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:80:29)\n at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\which\which.js:89:16\n at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\index.js:42:5\n at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\isexe\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:152:21)',
gyp verb which failed code: 'ENOENT' }
gyp verb could not find "python". checking python launcher
gyp verb could not find "python". guessing location
gyp verb ensuring that file exists: C:\Python27\python.exe
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-gyp\lib\configure.js:484:19)
gyp ERR! stack at PythonFinder. (C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-gyp\lib\configure.js:509:16)
gyp ERR! stack at C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\nodejs\node.exe" "C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-gyp\bin\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\DEV\sp-dev-solutions\solutions\ContactManagement\node_modules\node-sass
gyp ERR! node -v v8.9.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2018-09-03T03_50_05_787Z-debug.log

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

running NPM I or NPM INSTALL would download all the modules into node_modules folder, enabling the execution of the solution through GULP SERVE

I'm using NODE 8.9.4 (Currently using 64-bit executable)

Observed Behavior

several errors - I don't know what went wrong

Steps to Reproduce

C:\DEV\ git clone https://github.com/SharePoint/sp-dev-solutions.git {worked!]
C:\DEV\sp-dev-solutions\solutions\ContactManagement>npm i [partially failed]

Erros with SPHttp

Category

  • Bug

Expected or Desired Behavior

If you are reporting a bug, please describe the expected behavior. If you are suggesting an enhancement please describe thoroughly the enhancement, how it can be achieved, and expected benefit.

Observed Behavior

Getting the following error on gulp serve
Error - [tsc] src/services/NlpService/NlpService.ts(43,74): error TS2345: Argument of type 'HttpClientConfiguration' is not assignable to parameter of type 'HttpClientConfiguration'.
Error - [tsc] src/webparts/searchBox/SearchBoxWebPart.ts(123,45): error TS2345: Argument of type 'HttpClient' is not assignable to parameter of type 'HttpClient'.
Error - [tsc] src/webparts/searchResults/SearchResultsWebPart.ts(193,57): error TS2345: Argument of type 'SPHttpClient' is not assignable to parameter of type 'SPHttpClient'.
Error - [tsc] src/webparts/searchResults/SearchResultsWebPart.ts(534,79): error TS2345: Argument of type 'SPHttpClientConfiguration' is not assignable to parameter of type 'SPHttpClientConfiguration'.

Steps to Reproduce

Download the code, browse to the spfx folder, rup npm install and gulp serve

[Modern Search] Incorrect search query if use "Send query to a new page"

Hi @wobba , @FranckyC

Category

  • Question
  • [ x] Bug
  • Enhancement

Expected or Desired Behavior

Search result should process query from Search Box and Url string correctly.

Observed Behavior

I configured Search Box web part
image

It works if search term is single word like "fresh" but if I use "fresh produce" Search result web part on targeted page runs query for "fresh%20produce" and return incorrect results. So it doesn't decode query fragment "#" correctly.
image

We use 3.0.0.4 version

Thanks

Steps to Reproduce

Above

Console error: Unexpected token / in JSON at position 0 (In the Box button web part)

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Category

  • [0] Question
  • [1] Bug
  • [0] Enhancement

Expected or Desired Behavior

There should not be any errors logged in the console window

Observed Behavior

Following issue is logged in the console :
Uncaught (in promise) SyntaxError: Unexpected token / in JSON at position 0
at t.e.json (sp-pages-assembly_en-us_1ba58d40502a1529520e7281a1c23097.js:1189)

Steps to Reproduce

Separated the solution to include only box button and its required contents in a new solution.
Added this customised web part to a modern communication site page.
Added a link to a sharepoint site collection. as a button.
Each instance of this web part added causes this error to be logged.

Further investigation led to the fact its trying to log some text to a config file path:- /SiteAssets/webpart-logging.config. The file does not exists on this location and the contents which were to be logged are not yet investigated.

The complete error logged is as follows :
Uncaught (in promise) SyntaxError: Unexpected token / in JSON at position 0
at t.e.json (sp-pages-assembly_en-us_1ba58d40502a1529520e7281a1c23097.js:1189)
at box-button-web-part-bundle_fbbee451ac7adc73921901e319305b71.js:15

e.json @ sp-pages-assembly_en…281a1c23097.js:1189
  (anonymous) @
  Promise.then (async)  
  (anonymous) @
  Promise.then (async)  
  e.logUsage @
  t.onInit @
  t._internalRenderInViewPort @
  e._renderWebpartInViewport @
  e._checkVisibilityAndRender @
  e.register @
  t._internalDelayedRender @
  (anonymous) @
  t._internalFirstTimeRender @
  (anonymous) @
  Promise.then (async)  
  e._renderWebPart @
  (anonymous) @
  Promise.then (async)  
  (anonymous) @
  e.loadWebPart @
  t.componentDidMount @
  br @
  gr @
  yr @
  dr @
  ir @
  Cr @
  Er @
  window.spModuleLoader.Or.render @
  (anonymous) @
  xr @
  Ir @
  render @
  e._render @
  e.render @
  t._renderCanvas @
  (anonymous) @
  Promise.then (async)  
  t.componentDidMount @
  e. @
  br @
  gr @
  yr @
  dr @
  ir @
  Cr @
  Er @
  window.spModuleLoader.Or.render @
  (anonymous) @
  xr @
  Ir @
  render @
  t._renderInternalRouter @
  (anonymous) @
  Promise.then (async)  
  t.onRender @
  t._render @
  (anonymous) @
  Promise.then (async)  
  e._initializeApplication @
  e._initializeApplicationWithTelemetry @
  e.startApplication @
  e._runApplicationManager @
  e._executePlatformCode @
  e._startApplication @
  e.startApplication @
  e._startApplication @
  e._startApplication @
  (anonymous) @
  Promise.then (async)  
  e.start @
  startSpfx @
  (anonymous) @
  (anonymous) @

I could not run the site script for flows-formatters-pages-siteScripts

Hi everyone,

I try to create a team site using the provided site script 'UberSiteDesign.json' but the site script stuck on the initialising. I awaited for few minutes and it is still stick on that screen.

site-script-error

Category

  • Question
  • [x ] Bug
  • Enhancement

Expected or Desired Behavior

Expected to see the site script run successfully.

Observed Behavior

I have done some testing and and i found out that if i remove some of the lines in the scripts than it successfully created. I have tested by removing some chuck from different sections. This shows that the site script has some line, or character or size limits. Can some one clarify on this?

Steps to Reproduce

  1. Get the 'UberSiteDesign.json' from https://github.com/SharePoint/sp-dev-solutions/tree/master/solutions/flows-formatters-pages-siteScripts/site-designs.
  2. $siteScript = Get-Content '[[pathToYourSiteScriptJsonFile]]' -Raw
  3. $mySiteScript = Add-SPOSiteScript -Title "Classroom Site Script" -Description "Classroom Site Script" -Content $siteScript
  4. Add-SPOSiteDesign -Title "Classroom site designs" -WebTemplate "64" -SiteScripts $mySiteScript -Description "classroom site design"

I hope someone could guide me on this issue.

Thank you in advanced.

Can not build react-search-refiners

Hi Team,

I was trying to use Modern search related webparts.
I downloaded the code and as per instruction i run npm install and gulp serve however it shows blank screen.

When i create a project normally then it works fine. please suggest what issues could be.
my node version is 8.11.3
npm version is : 5.6.0
i get a lot of errors in console as below.
reactsearchrefiner

Thankyou in advance for your suggestions

[ModernSearch] Upgrade to SPFx v1.8.2

I'm planning to start the upgrade of the Modern Search to v1.8.1 of SPFx. Current plan are the following steps, if there are concerns/other approaches etc. let me know before I start ;)
@FranckyC @wobba

Todo

  • Upgrade to SPFX v1.8.2
  • Upgrade to TypeScript v3.3
  • Upgrade Office UI Fabric React

Can't run package-solution --ship on react-search-refiners

Category

  • Bug

Expected or Desired Behavior

Running from the spfx folder: npm install followed by gulp build --ship & gulp package-solution --ship should produce a build.

Observed Behavior

When just gulp build and gulp package-solution are used the package is generated successfully, with the addition of --ship, package-solution produces the following error:

Error - Error: The webparts manifests list is empty. Please ensure you have done a build and that your config file is pointed at the correct folder.
at Object.createPackage [as default] (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/@microsoft/sp-build-core-tasks/lib/packageSolution/packageSolution/createPackage.js:25:19)
at DestroyableTransform.gulp.src.pipe.through2.obj [as _flush] (C:/###/Documents/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/@microsoft/sp-build-core-tasks/lib/packageSolution/PackageSolutionTask.js:116:36)
at DestroyableTransform.prefinish (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:138:10)
at emitNone (events.js:106:13)
at DestroyableTransform.emit (events.js:208:7)
at prefinish (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:619:14)
at finishMaybe (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:627:5)
at endWritable (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:638:3)
at DestroyableTransform.Writable.end (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:594:41)
at DestroyableTransform.onend (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/vinyl-fs/node_modules/readable-stream/lib/_stream_readable.js:523:10)
Error - Error: The webparts manifests list is empty. Please ensure you have done a build and that your config file is pointed at the correct folder.
at Object.createPackage [as default] (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/@microsoft/sp-build-core-tasks/lib/packageSolution/packageSolution/createPackage.js:25:19)
at DestroyableTransform.gulp.src.pipe.through2.obj [as _flush] (C:/Users/###/Documents/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/@microsoft/sp-build-core-tasks/lib/packageSolution/PackageSolutionTask.js:116:36)
at DestroyableTransform.prefinish (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:138:10)
at emitNone (events.js:106:13)
at DestroyableTransform.emit (events.js:208:7)
at prefinish (C:/Users/caleb.stone/Documents/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:619:14)
at finishMaybe (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:627:5)
at endWritable (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:638:3)
at DestroyableTransform.Writable.end (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:594:41)
at DestroyableTransform.onend (C:/Users/###/SPFx-Webparts/ModernSearch/react-search-refiners/spfx/node_modules/vinyl-fs/node_modules/readable-stream/lib/_stream_readable.js:523:10)
Error - 'package-solution' sub task errored after 70 ms
No manifests were found in '*.json'. Ensure a build has completed successfully and that paths.manifestsMatch is correct

Steps to Reproduce

clone
cd spfx
npm install
gulp build --ship
gulp package-solution --ship

Hub Links web part (Grouped List) not formatting correctly

Category

  • Question
  • [X ] Bug
  • Enhancement

Expected or Desired Behavior

In a grouped list it was grouping under the category field and the user was able to collapse and expand each category. Now it does not allow collapsing or expanding and the down arrow at the end of the category is missing. Right below the category it shows a greater than and then a down arrow but they are not clickable.

Observed Behavior

Category is no longer collapsible
Web part does not finish loading when added to a page.

Steps to Reproduce

I downloaded the latest repo and then did a npm install. Then I opened the project in VS Code and debugged it. I also installed the web parts on a SharePoint Online tenant. When adding the Hub Links List web part to a page it just displays "Loading Hub Links List..." and never finishes loading.

Can't build latest version

Category

  • Question
  • [X ] Bug
  • Enhancement

Expected or Desired Behavior

I want to be able to build the project.

Observed Behavior

I downloaded the latest code, unzipped it, ran "npm install" and then tried to build it. I throws 2 errors:
Error - [tsc] src/webparts/handlebarTemplateDisplay/HandlebarTemplateDisplayWebPart.ts(24,36): error TS1149: File name 'S:/LinksAndHandlebarsTemplate/src/propertyPane/propertyPaneSearch/PropertyFieldSearch.ts' differs from already included file name 'S:/LinksAndHandlebarsTemplate/src/propertyPane/PropertyPaneSearch/PropertyFieldSearch.ts' only in casing.
[11:40:37] Error - 'tsc' sub task errored after 10 s
exited with code 2

that appear to be the same error. Is there something I'm missing?

Steps to Reproduce

  1. Download code
  2. Extract code
  3. run "npm install"
  4. run "gulp build"

[Modern Search] Date filter

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

Very nice additon with this date filter, clearly something our users were really asking for, thank you !!
But i found a few bugs around this functionnality :

  • i have several other refiners and when other refiners got recalculate to reflect the results filtered by date, my date choice is not displayed anymore
  • when i filter by date, my property "technical" name is shown below the filter button and not the actual date or at least the displayValue of the refiner...
    image

[ColumnFormatter 1.2] "self.require is not a function" error in Monaco editor

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

Downloaded the column-formatter.sppkg (version 1.2) file from the repo and installed it on my tenant.

Observed Behavior

After choosing the column type and the screen with the json formatting appears there is an error in the console and the intellisense for the json is not working. The error is from the index.js file in the MonacoCustomBuild folder. The same error appears after npm install and gulp serve on the repo source code. There is no such error after installing the previous version - column-formatter-1.1.0.0.sppkg

The error is:

TypeError: self.require is not a function
at index.js:4888
at new Promise_ctor (index.js:1962)
at EditorSimpleWorkerImpl.BaseEditorSimpleWorker.loadForeignModule (index.js:4887)
at index.js:6553
at ShallowCancelThenPromise.CompletePromise_then [as then] (index.js:1942)
at MonacoWebWorkerImpl._getForeignProxy (index.js:6553)
at MonacoWebWorkerImpl.getProxy (index.js:6553)
at e._getClient (index.js:8713)
at e.getLanguageServiceWorker (index.js:8713)
at e.c [as _worker] (index.js:8713)

Unable to build ColumnFormatter for production

Category

  • Question
  • Bug
  • Enhancement

Expected or Desired Behavior

I wish to package the solution for production, by running gulp build, gulp bundle --ship, gulp package-solution --ship

Observed Behavior

I run gulp build, then gulp --ship, at this point the process does not move beyond
Starting subtask 'webpack' ...

Steps to Reproduce

Running npm 6.1.0, node 8.11.1
Download solution
run npm install
run gulp build
run gulp bundle --ship

[ModernSearch] Search navigation Web Part should allow predefined queries

Category

  • [ X] Enhancement

Expected or Desired Behavior

@taraldga Instead of relying on a search box, you could also add a mode where tabs correspond to predefined queries and use the URLFragment (or other configurable option like a query string parameter) to pass them. It could be very useful to enable single search page scenarios with query rules and result types depending the query.

Also add the sorting option on tabs (PropertyFieldCollectionData). It could useful as well.

Also use a placeholder on first configuration. Right now it feels like there is a bug or something since the Web Part shows nothing.

Hub web parts sppkg not linking to existing lists

Category

  • Question
  • [X ] Bug
  • Enhancement

Expected or Desired Behavior

I want to use lists to populate the Hub webparts sppkg.

Observed Behavior

Lists aren't pulled in even though I'm selecting existing lists on my site. I was only able to pull in one list using buttons, and that one was limited to a blue, bold, all caps design.

Steps to Reproduce

  • Add hub-web-parts.sppkg to app catalog.
  • Add web part to site collection.
  • Use any of the three web parts in modern page on site collection.
  • Enable list mode, choose existing list.

Submission Guidelines

Thumbnail picture of is not coming using search refiner

I have created one news article page and there I have added one Thumbnail picture. Now when i am trying to fetch the the news post in other page using search refiner everything is coming except that thumbnail pictute.

I have added PublishingImage as managed propoerty.
Here is the code:

<div class="template_result">
                               // <img height="60" width="70" style="padding-right:10px" src="{{PublishingImage}}">
                               <div class="template_contentContainer">
                                <span class=""><a href="{{getUrl item}}">{{Title}}</a></span>
                                <span class="">{{getSummary HitHighlightedSummary}}</span>
                                <span class=""><span>{{getDate Created "LL"}}</span></span>   
                                <div class="tags_736e27a1">

But the picture is not coming. I did inspect element.. I am getting picture url but still picture is not appearing.
this is the inspect element scenario :

<img height="60" width="70" style="padding-right:10px" src="<img alt=""<src="/news/PublishingImages/Chaand-Nagpaul.jpg" style="BORDER&amp;0px solid;" />

Can you please tell me what i am missing here. Thanks in advance.

[ModernSearch] Regression with pagination

Expected or Desired Behavior

If you have multiple pages of search results and select a page, when selecting a refiner I expect to be returned to the first page of search results.

Observed Behavior

The selected page "sticks", and when there aren't any search results on that page it will show the no results message and no page selected in the pages webpart.

Steps to Reproduce

Steps to be executed in the local workbench:

  • Add a searchbox, search results, search refiners and search pagination web part on the page and connect them.
  • Show only 1 search result per page
  • Switch to page 4
  • Apply refiner on Type, and select "Document"

Result: paging webpart shows 2 available pages, but no results are shown.

Reason

@FranckyC the changes you made in #94 cause this regression, specifically those done in componentWillReceiveProps of SearchResultsContainer.tsx. Can you look at this?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.