"Expected identifier, string or number" when trying to execute electron-forge 6.0.0-beta.62

[DManstrator]

Pre-flight checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project uses.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version

6.0.0-beta.62

Electron version

v12.2.3

Operating system

Windows 10 (21H2)

Last known working Electron Forge version

6.0.0-beta.61

Expected behavior

I expect Electron Forge to run through and not throw an exception.

Actual behavior

When using npm start, I immediately get a compilation error.

File: node_modules/@electron-forge/cli/dist/electron-forge.js
Error: Expected identifier, string or number (line 15, pos 79)
Code:

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }
                                                                             ^

Steps to reproduce

1. npm install (see package.json below)
2. npm start -> executes electron-forge start

Additional information

Logs / Stacktrace

Even when using npm start --verbose I get nothing useful. Setting the debug flag doesn't change anything either.

cmd line args

electron-forge start

package.json

{
  "name": "Electron-Browser",
  "version": "1.0.0",
  "main": "main.js",
  "private": true,
  "devDependencies": {
    "@electron-forge/cli": "6.0.0-beta.62",
    "@electron-forge/maker-deb": "6.0.0-beta.62",
    "@electron-forge/maker-rpm": "6.0.0-beta.62",
    "@electron-forge/maker-squirrel": "6.0.0-beta.62",
    "@electron-forge/maker-zip": "6.0.0-beta.62",
    "electron": "12.2.3",
    "electron-rebuild": "3.2.5"
  },
  "dependencies": {
    "colors": "1.4.0",
    "electron-default-menu": "1.0.2",
    "electron-log": "4.4.3",
    "electron-settings": "4.0.2",
    "electron-squirrel-startup": "1.0.0",
    "java": "0.12.1"
  },
  "scripts": {
    "start": "electron-forge start",
  }
}

When comparing the electron-forge.js files between those two version, there are just 2 difference:

• In 6.0.0-beta.62, colors is not used anymore (for a good reason).
• In 6.0.0-beta.61, the file starts with #!/usr/bin/env node (v62 doesn't do this).

I would be glad for any help. For now I stay on 6.0.0-beta.61 and added colors at version 1.4.0 to be not affected by the recent events. If you need more information let me know it.

Kind regards,

DMan

[malept]

Duplicate of #2670

[DManstrator]

I'm sorry, I just checked for open issues since this version was released very recently. I didn't expect that this was already reported or even fixed. Will remember that next time I open an issue.

I can confirm that version 6.0.0-beta.63 fixed my issue. Sorry for the issue.