You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same issue, but now with the Monaco Editor-bundled version 3.3 (without e.g. readonly tuples feature) vs. current version 3.4.
Is there a possibility to use the TypeScript language service (typescriptServices.js) from the typescript npm package instead of the bundled one (.../monaco-editor/esm/vs/language/typescript/lib/typescriptServices.js) without forking Monaco Editor?
The text was updated successfully, but these errors were encountered:
@alexandrudima Is there any possibility? I'm really struggling with the semantic model errors when using TS 3.4 declarations containing readonly tuples and arrays...
... if there is no (easy) possiblity ... when can expect a Monaco Editor release containing TS 3.4 (or 3.5)?
It is possible to fork monaco-typescript and publish it to npm as monaco-typescript-fork. Then, it is possible to fork this project and tweak the monaco-typescript plugin section here --
This is a follow-up of #177.
Same issue, but now with the Monaco Editor-bundled version 3.3 (without e.g.
readonly
tuples feature) vs. current version 3.4.Is there a possibility to use the TypeScript language service (
typescriptServices.js
) from thetypescript
npm package instead of the bundled one (.../monaco-editor/esm/vs/language/typescript/lib/typescriptServices.js
) without forking Monaco Editor?The text was updated successfully, but these errors were encountered: