Repository navigation
Typescript Errors in Backend #212
Description
Currently I am seeing lots of typescript errors in the backend package.
I wasn't sure I could confirm these errors since they don't always appear and I think it has to do with this being a monorepo. Maybe you can help confirm that these are real. But when I go to packages/backend and I run pnpm tsc --noEmit I get the following:
Found 79 errors in 15 files.
Errors Files
51 src/altNodes/jsonNodeConversion.ts:203
3 src/altNodes/oldAltConversion.ts:80
6 src/common/commonPosition.ts:7
5 src/common/retrieveUI/retrieveColors.ts:88
1 src/flutter/builderImpl/flutterBlend.ts:62
1 src/flutter/flutterContainer.ts:50
1 src/flutter/flutterDefaultBuilder.ts:32
1 src/flutter/flutterMain.ts:148
1 src/flutter/flutterTextBuilder.ts:79
1 src/html/builderImpl/htmlBlend.ts:115
1 src/swiftui/builderImpl/swiftuiBlend.ts:33
2 src/swiftui/builderImpl/swiftuiColor.ts:53
2 src/tailwind/tailwindDefaultBuilder.ts:96
2 src/tailwind/tailwindMain.ts:224
1 src/tailwind/tailwindTextBuilder.ts:76
Activity
bernaferrari commentedon Mar 22, 2025
This is expected. This was one of the reasons I didn't want to merge the new version. Basically we now use the REST API which is completely different, but half the plugin still uses the old API, and not only that but we still have a toggle to switch between old and new.
But yes, it makes sense over time to remove the figma plug-in types, then migrate to the new API and see what survives. After that we need to extend some types (AltNodes here we go again), but the big change is switch from the old API to the new one.