So microsoft/fast 2.0 is out or what?

[jurijsk]

I want to share a bit of developer experience with all of you (As ex-dev, trying to get back to coding).

I've decided to try to use the library, so I go to https://fast.design/ and the badge to the top says 2.0 is out. Drop-down with version number says "2.x". Great, very promising.

Span off new vanilla vite project with typescript, ran npm install @microsoft/fast-element and copied the code as Quick Start advices.

Got 3 errors right away:

I had to google profusely to just make it compile. Added experimentalDecorators: true, switched module, target to ES2020 and 'strict' to false. Plus change HelloWorld.define({..,}) to HelloWorld.define(HelloWorld, {...}). Just. To. Make. It. Compile.

And it still was not working after that. The name attribute was not taking the value. You have to find this issue from 2021 to know that you have to switch useDefineForClassFields off, otherwise the whole enterprise is kind of useless.

And only after that, I had a bright idea to check with the version of fast I have installed. Of course, it was 1.14.0, why would I think it would be anything close to 2.0.

Anyway, so what is up with v2.0 and is that experience I've just got is what I should expect from microsoft/fast as a base for UI I want to build?

[KingOfTac]

There was a recent publish of the 1.x version to fix a bug, which with how npm install works the most recently published version of the package is what gets installed by default. You can get the latest 2.x version by specifying the version number when installing i.e. npm install @microsoft/fast-element@2.0.0.

@chrisdholt we should probably look into this some more and try to find a way to smooth out this experience. I have noticed this also affects what version is returned when using the CDN link as well.

[chrisdholt]

@chrisdholt we should probably look into this some more and try to find a way to smooth out this experience. I have noticed this also affects what version is returned when using the CDN link as well.

This came up with @janechu yesterday, it's definately top of mind.

[jurijsk]

Thank you for looking into this. Please note that the following tsconfig.ts settings are also assumed, and it takes a minute to figure out:

{
	"compilerOptions": {
		//...
		"useDefineForClassFields": false,
		"strictPropertyInitialization": false,
		"experimentalDecorators": true
	}
}