fix traced warnings from unexpected token (#6810)

* fix traced warnings from unexpected token

* Failed to parse

Co-authored-by: Rich Harris <hello@rich-harris.dev>

* fix lint

* add changeset

Co-authored-by: Rich Harris <hello@rich-harris.dev>

Author: styfle

.changeset/immaculate-error-handler.md

@@ -0,0 +1,6 @@
+---
+'@sveltejs/adapter-vercel': patch
+---
+
+Ignore warnings when traced file fails to parse
+

packages/adapter-vercel/index.js

@@ -308,6 +308,11 @@ async function create_function_bundle(builder, entry, dir, runtime) {
 		// pending https://github.com/vercel/nft/issues/284
 		if (error.message.startsWith('Failed to resolve dependency node:')) return;
 
+		// parse errors are likely not js and can safely be ignored,
+		// such as this html file in "main" meant for nw instead of node:
+		// https://github.com/vercel/nft/issues/311
+		if (error.message.startsWith('Failed to parse')) return;
+
 		if (error.message.startsWith('Failed to resolve dependency')) {
 			const match = /Cannot find module '(.+?)' loaded from (.+)/;
 			const [, module, importer] = match.exec(error.message);