Compile problem with langium sprotty and 4.0.1

[cdietrich]

Hi, is there a reason there is no langium-sprotty 4.0.1
with the mixed versions we now see compile errors with

error TS2352: Conversion of type 'LangiumCoreServices' to type 'LangiumSprottyServices' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type 'LangiumCoreServices' is not comparable to type 'LangiumDefaultCoreServices'.
    The types of 'parser.LangiumParser' are incompatible between these types.
      Type 'import("/Users/dietrich/lotse-script/node_modules/langium/lib/parser/langium-parser", { with: { "resolution-mode": "import" } }).LangiumParser' is not comparable to type 'import("/Users/dietrich/lotse-script/node_modules/langium-sprotty/node_modules/langium/lib/parser/langium-parser", { with: { "resolution-mode": "import" } }).LangiumParser'.
        Types have separate declarations of a private property 'linker'.

161         const language = this.serviceRegistry.getServices(doc.uri) as LangiumSprottyServices
            

(regen yarn lock for the new range does help as a workaround, dependabot ususally does not do it)

[msujew]

Hey @cdietrich,

It seems like dependabot didn't do something correctly. It seems like langium-sprotty was still pulling in [email protected], but you also had a dependency to [email protected]. Two versions of langium in the same build will always lead to issues. In your case build issues, but in other cases it will likely lead to runtime problems. Only one version of Langium should be pulled across one project.

[cdietrich-everest]

Yes this is why regenerate yarn lock helps

[cdietrich]

@msujew tag is also missing

[cdietrich]

@msujew same for 4.0.3

[msujew]

I've pushed the tags 👍