Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error - [webpack] 'dist': ./node_modules/micromark-util-decode-numeric-character-reference/index.js 23:11 Module parse failed: Identifier directly after number #161

Closed
4 tasks done
Hasni501 opened this issue Dec 5, 2023 · 12 comments
Labels
🤷 no/invalid This cannot be acted upon 👎 phase/no Post cannot or will not be acted on

Comments

@Hasni501
Copy link

Hasni501 commented Dec 5, 2023

Initial checklist

Affected packages and versions

using node 18.17.1

Link to runnable example

No response

Steps to reproduce

I am using botframework-webchat and when i try to build it, the below error message pop-ups.

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/lib/markdown/private/iterateLinkDefinitions.js
@ ./node_modules/botframework-webchat/lib/markdown/renderMarkdown.js
@ ./node_modules/botframework-webchat/lib/index.js
@ ./lib/extensions/chatbotExtension/renderer/Chatbot.js
@ ./lib/extensions/chatbotExtension/renderer/ChatbotPanel.js
@ ./lib/extensions/chatbotExtension/ChatbotExtensionApplicationCustomizer.js
./node_modules/micromark-util-sanitize-uri/index.js 86:22

Expected behavior

the package should build sucessfully

Actual behavior

currently its giving error while running npm build

Runtime

Node v16

Package manager

npm v7

OS

Windows

Build and bundle tools

Webpack

@JounQin
Copy link
Member

JounQin commented Dec 5, 2023

Which webpack version are you using? And, please, provide an online runnable reproduction.

@JounQin JounQin transferred this issue from micromark/.github Dec 5, 2023
@github-actions github-actions bot added 👋 phase/new Post is being triaged automatically 🤞 phase/open Post is being triaged manually and removed 👋 phase/new Post is being triaged automatically labels Dec 5, 2023
@wooorm
Copy link
Member

wooorm commented Dec 5, 2023

use modern webpack / use babel to compile modern code to work in old javascript engines.
We support modern code/Node, as mentioned in the readme

@wooorm wooorm closed this as completed Dec 5, 2023
@wooorm wooorm added the 🤷 no/invalid This cannot be acted upon label Dec 5, 2023

This comment has been minimized.

@github-actions github-actions bot added 👎 phase/no Post cannot or will not be acted on and removed 🤞 phase/open Post is being triaged manually labels Dec 5, 2023
@Hasni501
Copy link
Author

Hasni501 commented Dec 5, 2023

Which webpack version are you using? And, please, provide an online runnable reproduction.

webpack-cli ^5.1.4

@JounQin
Copy link
Member

JounQin commented Dec 5, 2023

Again, an online runnable reproduction is required.

@Hasni501
Copy link
Author

Hasni501 commented Dec 5, 2023

Again, an online runnable reproduction is required.

https://github.com/Hasnii501/app-extension.git

@micromark micromark deleted a comment from Hasni501 Dec 5, 2023
@JounQin
Copy link
Member

JounQin commented Dec 5, 2023

@Hasni501 You're still using webpack@4 in the reproduction repository.

@Hasni501
Copy link
Author

Hasni501 commented Dec 5, 2023

@Hasni501 You're still using webpack@4 in the reproduction repository.

Im a newbie, am sorry, but I am unable to understand this, can you please the steps to fix it?

@JounQin
Copy link
Member

JounQin commented Dec 5, 2023

use modern webpack / use babel to compile modern code to work in old javascript engines.
We support modern code/Node, as mentioned in the readme

@wooorm
Copy link
Member

wooorm commented Dec 5, 2023

There are a ton of resources about webpack and other tools on the internet. You can do some research and try some tinkering yourself. That's how you learn ;)

@Hasni501
Copy link
Author

Hasni501 commented Dec 6, 2023

use modern webpack / use babel to compile modern code to work in old javascript engines.
We support modern code/Node, as mentioned in the readme

I am using SharePoint Online SPFX framework, its not native react application.

@micromark micromark locked as off-topic and limited conversation to collaborators Dec 6, 2023
@ChristianMurphy
Copy link
Member

@Hasni501 adding on a bit.
It is an issue in the build tool, and is very specific to SharePoint rather than micromark.
SharePoint has their own support forum at https://sharepoint.stackexchange.com/search?q=webpack which has a number of related issues which may help you track down the issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🤷 no/invalid This cannot be acted upon 👎 phase/no Post cannot or will not be acted on
Development

No branches or pull requests

4 participants