Fix "Module parse failed" errors on Windows

[neeh]

I encountered these errors when building on Windows:

• Module parse failed: Invalid escape sequence
• Module parse failed: Octal literal in strict mode

It seems to be caused by the backslash characters of Windows paths. Those are treated as either an escape sequence (e.g. \n) or an octal literal (e.g. \345) by JS.

Replacing backslash characters with forward slash characters in the exported file path fixed the issue.

[haversnail]

Seems straightforward enough; thanks for fixing!

Edit: after some investigation, it seems a more resilient/conventional way to handle this would be to use the posix object to ensure the correct separators are used, e.g.:

-  const fullPath = path.join(publicPath, interpolatedPath).replace(/\\/g, '/');
+  const fullPath = path.posix.join(publicPath, interpolatedPath);

Can you confirm if this approach also resolves your specific issue? If so, feel free to update the PR to use the posix implementations where path is used and I can approve/merge. 👍

[neeh]

I tested your suggestion but this didn't work because the strings to join also have the backslash themselves:

path.join('my\\path', 'to\\model.gltf'); // 'my\\path\\to\\model.gltf'

path.posix.join('my\\path', 'to\\model.gltf'); // 'my\\path/to\\model.gltf'

path.join('my\\path', 'to\\model.gltf').replace(/\\/g, '/'); // 'my/path/to/model.gltf'