microsoft / microsoft/CopilotStudioSamples
SharePoint SSO Component deployment fails using Azure DevOps
@adilei is already working on this.
Since May 21, 2024.
- Dominant language
- TypeScript
- Stars
- 797
- Forks
- 491
- PR merge metrics
- No merged PRs in 30d
Description
What sample tool are you using?
SharePoint SSO Component
Describe the bug
I'm having issue to deploy SharePoint SSO Component sample using Azure DevOps when using VM ubunto-latest
To Reproduce
Steps to reproduce the behavior:
add the yaml file required to automate the sample deployment in Azure DevOps using ubuntu-latest VM
stages:
- stage:
displayName: build
jobs:
- job:
displayName: build
pool:
vmImage: ubuntu-latest
demands:
- npm
- node.js
- java
Expected behavior
Expected to get the sample build smoothly as it was build locally
Screenshots
Error:
Error - [webpack] 'dist':
./node_modules/micromark-util-decode-numeric-character-reference/index.js 23:11
Module parse failed: Identifier directly after number (23:11)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| code > 126 && code < 160 ||
| // Lone high surrogates and low surrogates.
> code > 55_295 && code < 57_344 ||
| // Noncharacters.
| code > 64_975 && code < 65_008 || /* eslint-disable no-bitwise */
@ ./node_modules/mdast-util-from-markdown/lib/index.js 138:0-97 1061:14-45
@ ./node_modules/mdast-util-from-markdown/index.js
@ ./node_modules/botframework-webchat-component/lib/Attachment/Text/private/LinkDefinitions.js
@ ./node_modules/botframework-webchat-component/lib/Attachment/Text/private/MarkdownTextContent.js
@ ./node_modules/botframework-webchat-component/lib/Attachment/Text/TextContent.js
@ ./node_modules/botframework-webchat-component/lib/index.js
@ ./node_modules/botframework-webchat/lib/addVersion.js
@ ./node_modules/botframework-webchat/lib/index.js
@ ./lib/extensions/copilotComponent/components/ChatBot.js
@ ./lib/extensions/copilotComponent/CopilotComponentApplicationCustomizer.js
./node_modules/micromark-util-sanitize-uri/index.js 86:22
Module parse failed: Identifier directly after number (86:22)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| }
| // Astral.
> else if (code > 55_295 && code < 57_344) {
| const next = value.charCodeAt(index + 1)
|
@ ./node_modules/micromark/lib/compile.js 44:0-55 770:10-21 781:10-21 1089:8-19 1105:22-33
@ ./node_modules/micromark/index.js
@ ./node_modules/mdast-util-from-markdown/lib/index.js
@ ./node_modules/mdast-util-from-markdown/index.js
@ ./node_modules/botframework-webchat-component/lib/Attachment/Text/private/LinkDefinitions.js
@ ./node_modules/botframework-webchat-component/lib/Attachment/Text/private/MarkdownTextContent.js
@ ./node_modules/botframework-webchat-component/lib/Attachment/Text/TextContent.js
@ ./node_modules/botframework-webchat-component/lib/index.js
@ ./node_modules/botframework-webchat/lib/addVersion.js
@ ./node_modules/botframework-webchat/lib/index.js
@ ./lib/extensions/copilotComponent/components/ChatBot.js
@ ./lib/extensions/copilotComponent/CopilotComponentApplicationCustomizer.js
./node_modules/htmlparser2/lib/esm/index.js 48:9
Module parse failed: Unexpected token (48:9)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| * They should probably be removed eventually.
| */
> export * as ElementType from "domelementtype";
| import { getFeed } from "domutils";
| export { getFeed } from "domutils";
@ ./node_modules/sanitize-html/index.js 1:19-41
@ ./node_modules/botframework-webchat/lib/markdown/renderMarkdown.js
@ ./node_modules/botframework-webchat/lib/index.js
@ ./lib/extensions/copilotComponent/components/ChatBot.js
@ ./lib/extensions/copilotComponent/CopilotComponentApplicationCustomizer.js
Additional context
It gets build if I change the VM to be windows-latest
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.