vscode/build/monaco
Alex Dima 135c473ddf Fixes #77454:
- do not cary over unnecessary "extends" in tsconfig.json
- keep members ending with `Brand`, but do it at the right phase
- remove shorthand literal usage which confuses tree-shaker
- add back noImplicitAny
2019-07-29 15:39:29 +02:00
..
api.js Fixes #77454: 2019-07-29 15:39:29 +02:00
api.ts Fixes #77454: 2019-07-29 15:39:29 +02:00
LICENSE Better support for ESM workers 2018-03-15 14:44:36 +01:00
monaco.d.ts.recipe Add generated warning to monaco 2019-07-22 13:08:21 -05:00
monaco.usage.recipe Update monaco build recipt. 2019-07-25 13:01:36 -07:00
package.json monaco-editor-core@0.16.0 2019-03-02 02:35:13 +01:00
README-npm.md Ship README.md with monaco-editor-core 2016-06-09 11:20:03 +02:00
README.md Generate monaco.d.ts continuously and check it in build 2016-06-10 18:40:32 +02:00
ThirdPartyNotices.txt monaco-editor-core@0.16.0 2019-03-02 02:35:13 +01:00
version.txt monaco-editor-core@0.16.0 2019-03-02 02:35:13 +01:00

Steps to publish a new version of monaco-editor-core

Generate monaco.d.ts

  • The monaco.d.ts is now automatically generated when running gulp watch

Bump version

  • increase version in build/monaco/package.json

Generate npm contents for monaco-editor-core

  • Be sure to have all changes committed and pushed to the remote
  • (the generated files contain the HEAD sha and that should be available on the remote)
  • run gulp editor-distro

Publish

  • cd out-monaco-editor-core
  • npm publish