Uncaught SyntaxError: Invalid or unexpected token
See original GitHub issuemy webpack config
new ModuleFederationPlugin({
name: "ahas_sentinel",
library: { type: "var", name: "ahas_sentinel" },
filename: "remoteEntry.js",
remotes: {
ahas_switch: `ahas_switch@${config.output.publicPath}remoteEntry.js`,
},
exposes: {
"./routes": "./routes.tsx",
},
shared: {
...deps,
},
})
- webpack-5
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
SyntaxError: Unexpected token - JavaScript - MDN Web Docs
The JavaScript exceptions "unexpected token" occur when a specific language construct was expected, but something else was provided.
Read more >Uncaught SyntaxError: Invalid or unexpected token
@Iman's backtick(`) solution worked great in the modern browsers but caused an invalid character error in Internet Explorer. I had to use the...
Read more >Have a JavaScript Unexpected Token Error? Check Your Syntax
The JavaScript's parser expects tokens and symbols in a particular order, with relevant values or variables in between. Often, an Unexpected ...
Read more >JavaScript SyntaxError: Invalid or unexpected token ... - IBM
Given that you say the same exact task, if you re-issue it with the same exact data will then work, this feels like...
Read more >Uncaught SyntaxError: Invalid or unexpected token
[This thread is closed.] Console is showing this error after turning on minify css: Uncaught SyntaxError: Invalid or unexpected token Looking at the…...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
JSON.stringify(‘app2@http://example.com/’)
This seems to only happen with
{ library: { type: 'var', name: 'name' } }
. Not sure what the underlying reason is.