Open cuonghuunguyen opened 1 year ago
I only get this error in the editor when I open both d.ts files, but not from tsc or webpack.
did you use skipLibCheck for sth that ignore the error? if not could you show me the example how you archive that?
samples/browser-esm-webpack-typescript
I tried this one
Hi @hediet , after investigating, we found out that we have used the monaco.d.ts for the global monaco type by reference /// <reference path="../node_modules/monaco-editor/monaco.d.ts" />
However, I think this is still an issue if we want to have typesafe with monaco global when using monaco loader. And there are no examples of doing that in your repo. If you consider this to be a bug, I can change the title of this issue.
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
tsc
or fork-ts-checker-webpack-plugin.Expected behavior Compile successfully
Actual behavior Cannot compile due to the error
The reason behind this is you are coping declaration file in
monaco.d.ts
toeditor.api.d.ts
in https://github.com/microsoft/vscode/blob/c248f9ec0cf272351175ccf934054b18ffbf18c6/build/gulpfile.editor.js#L303-L320Please fix it so we can compile the apps that use
monaco-editor-core