0.0.18

Patch Changes

• 4a62337: fix: make config.esbuild.defineEnv possible to use

0.0.17

Patch Changes

• b8fca07: Fix: prepend ids to configuration properties correctly when using configuration from type
• 7333af5: docs: update readme and fix link to docs
• b8fca07: BREAKING rename configurationTypeGenerated.ts to configurationTypeCache.ts
• Updated dependencies [e65bed3]
  • typed-vscode@0.0.4

0.0.16

Patch Changes

• d4d743f: Fix: don't crash on configurationType.ts and generate types properly
• d4d743f: Fix gitignore command output. Also add generated variant of configuration
• d4d743f: Update typed-vscode to fix postinstall
• Updated dependencies [d4d743f]
  • typed-vscode@0.0.3

0.0.15

Patch Changes

• 5856aec: fix: add missing kleur dep...
• 5856aec: add vscf shortcut to vscode-framework (bin)
• Updated dependencies [5856aec]
  • vscode-manifest@0.0.8
  • typed-vscode@0.0.1

0.0.14

Patch Changes

• 9a642b3: BREAKING: In start and build command: rename option --path to --out
• 9a642b3: BREAKING remove startExtensionDevelopment export from index (cli only)
• 4b273c7: Feature: support having different esbuild config for development and production modes. Example: {esbuild: {production: {minify: true}}}
• 9a642b3: launch command accepts --cwd option
• a4b07ad: Fix issue where postinstall script where not generating types because of incorrect cwd. Now everything seems to be working
• 9a642b3: fix: unlink issues on windows
• 5b5b266: esbuid: print metafile import-graph
• 9a642b3: sourcemaps are now generated by default in start command

0.0.13

Patch Changes

• 16df6b2: Fix issues where start command was failing due to absence of out dir
• 3ced0b0: fix: enable back postinstall script to generate types on framework install
• 3ced0b0: Introduce absolutely new and clean configuration type generator which should be precise and fast for any configuration schema.
• 3ced0b0: Now you can type R in console to reload extension development window or launch vscode if extension connection is not found. Extension might be disconnected because development window isn't open or because extension encountered an error and connection was lost
• Updated dependencies [65e1a03]
  • vscode-manifest@0.0.7

0.0.12

Patch Changes

• Updated dependencies [bcbce6d]
• Updated dependencies [bcbce6d]
  • vscode-extra@0.0.4

0.0.11

Patch Changes

• c1d8819: Fix critical regression where extensions were unable to launch because injected variable was removed. I knew that it might happen, but unforunately I updated snapshot of injected code carelessly

0.0.10

Patch Changes

• Continue to publish on next tag. First changelog line!
• Updated dependencies [undefined]
  • vscode-manifest@0.0.5

0.0.9

Patch Changes

• 2c96acc: Fix issues where vscode-framework couldn't be imported in foreign environments. This was done by adding a check if variable, that should be injected to the code later by the our bundler actually exists