Does anyone run into Unexpected token (2:19)?

[adaliszk]

While I will open a proper issue about this later with a dummy project, I wanted to ask if anyone has run into this before?

When a session opens for Vite, the remotes throw out a Syntax Error onto the console:

SyntaxError: Unexpected token (2:19)
    at pp$4.raise (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:23636:13)
    at pp$9.unexpected (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:20930:8)
    at pp$9.semicolon (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:20907:66)
    at pp$8.parseExpressionStatement (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:21390:8)
    at pp$8.parseStatement (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:21123:24)
    at pp$8.parseTopLevel (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:20987:21)
    at Parser.parse (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:20759:15)
    at Function.parse (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:20809:35)
    at TransformContext.parse (file:/{{PROJECT_PATH}}/node_modules/vite/dist/node/chunks/dep-dc88b587.js:25955:27)
    at TransformContext.transform ({{PROJECT_PATH}}/node_modules/@originjs/vite-plugin-federation/dist/index.js:2450:32) {
  pos: 20,
  loc: Position { line: 2, column: 19 },
  raisedAt: 21
}

It does not break any behaviour as far as I could tell, but it does spam the console output. For some context: The host project is with Vue 3, the remotes are Lit components, and all of them are through a self-signed TLS connection. Everything is on the latest version, Vite is on alpha, but it did the same with the latest too.

[ruleeeer]

I went and looked and the approximate location of the error reported is here (if you're using the latest version of the plugin)

try {
      ast = this.parse(code);
}  catch (err) {
      console.error(err);
}

this.parse is the method provided by rollup to parse the code into ast. I suspect there is something special written to cause this behavior, but I'm not sure and may need a simple demo to see exactly what the problem is.

[adaliszk]

Hmm, one thing I can already see there is that it would be helpful if that console print would also print the code in question that failed, perhaps only with a specific flag enabled to avoid spamming even more. There seems to be no guarantee that the error contains the necessary information to track down what goes wrong.

As for the repro project, my week is quite busy, but I want to get to it by the weekend for sure.