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
Right now we majorly rely on maintainers to do testing and sanity checks before every release manually. Considering that we now support both AMD and ESM and we have 5 built in extensions shipped with Monaco Editor, an automatic build and test pipeline can help us avoid shipping broken bits as much as possible.
Fetch master from VS Code and build Monaco Editor core from it
Throw when build and tree shaking fails
Test the core and ensure the basic functionalities work
@orta thanks, I like the nightly build setup, only one question, it will publish monaco-editor nightly with monaco-editor-core from NPM and TypeScript nightly, right? In my setup, it's the other way around: we bundle monaco-editor-core from vscode master and monaco-typescript from NPM, run tests against it to see if there are any potential bugs.
Right now we majorly rely on maintainers to do testing and sanity checks before every release manually. Considering that we now support both AMD and ESM and we have 5 built in extensions shipped with Monaco Editor, an automatic build and test pipeline can help us avoid shipping broken bits as much as possible.
CI configuration is defined in https://github.com/microsoft/monaco-editor/blob/master/.github/workflows/ci.yml
The text was updated successfully, but these errors were encountered: