Sergei Sergeev

FYI I assumed you use SPFx 1.15, if not, then please tell me the version you use.

Closing as 1.15.4 version is published.

It might fail for the first compilation, but after the corresponding "HelloWorld.module.scss.d.ts" is updated, it compiles again and this time successfully, At least that's what I have on Win10 and...

whoa... very strange behavior. It's like fast-serve doesn't see your changes and it should fail on the first change, but it works. Could you then answer a few questions \...

Could you also do the test with SPFx 1.15, node 14.19 and spfx-fast-serve-helpers 1.15.0?

Sorry for asking you again, but we found that configuration - node 14.19(.1) and SPFx 1.15 (and spfx-fast-serve-helpers 1.15.0) - **WORKS** - node 16.16.0 / SPFx 1.15 / spfx-fast-serve 1.15.0...

Also, could you say which npm version do you use when test with node 16.16.0 and node 14.19(.1)?

@gandjustas consider [gulp-spsave](https://github.com/s-KaiNet/gulp-spsave) for both online and on prem. It uses sligtly different approach.

When it comes to `node-sp-auth`, then if you have 2FA enabled for your account, you can't use username \ password authentication directly. There are three workarounds: 1. Use add-in only...

BTW I saw this error when trying to run `node-sp-auth-config` from environment, where prompts are not supported, i.e. vscode add-in. I believe the same might apply to Visual Studio task...