Upgrade SPFx version, CLI command for file generation leads to encoding problem

[tabit01]

I used this command in the latest PowerShell, to generate the file. The result was a opaque encoding problem that popped up as an error message when running gulp serve --nobrowser. The solution was to copy the file content from the command, and create the file manually. I suggest adding that as an alternative method in the upgrade report.

FN015008 .eslintrc.js | Required

Add file .eslintrc.js

Execute the following command:

@'
require('@rushstack/eslint-config/patch/modern-module-resolution');
export default {
  extends: ['@microsoft/eslint-config-spfx/lib/profiles/react'],
  parserOptions: { tsconfigRootDir: __dirname }
};
'@ | Out-File -FilePath ".eslintrc.js"

[milanholemans]

Hi, @tor-axbit, what is exactly the encoding issue? The code you provided seems to work just fine in PowerShell, no?

[tabit01]

Well, I upgraded severall packages since I first got that error, so the trace is lost. There was something like SyntaxError: Unexpected token $#@ at new Script (node:vm:100:7)
I tried several approaches in the beginning, both CLI command and manually copying, I might have goofed. To me though, the file content looked perfectly fine when the error occured. And I read somewhere that PS command line file generation can cause encoding errors. My suggestion is simple, just add a warning to delete file, then manually copy file content if such errors happen.

[milanholemans]

From what version to which version did you upgrade? It looks odd to me if the file contents are exactly the same, which causes an issue. I don't see any non-ASCII chars whatsoever.

[tabit01]

from 1.17.4 to 1.19.0

[milanholemans]

AFAIK, there are no .eslintrc.js modifications when upgrading from 1.17.4 to 1.19.0