Skip to content

Latest commit

 

History

History
34 lines (21 loc) · 1.76 KB

README.md

File metadata and controls

34 lines (21 loc) · 1.76 KB
Raw

Example VS Code Extension with Fable

This is the Word Count example build with Fable. It was cloned from acormier/vscode-fable-sample and modified to work with the .NET SDK 3 and later, Rollup instead of Webpack and Fable 3.

For Extension Authors

Remember to update package.json and things like the license according to your needs.

Getting Started

Run the following commands:

# Restore .NET tools
dotnet tool restore
# Restore JavaScript packages
npm install

Now, open VS Code and hit F5 to start another instance of VS Code. This experimental instance will have the extension loaded and the debugger attached to it. When starting the "Launch Extension" configuration, VS Code will run the build NPM script, which will transpile and bundle the source code and write the resulting JavaScript code to the out/ directory.

Rebuild The Extension On Any Code Change

Run the "Build extension in watch mode" task from within VS Code. Alternatively, you can run npm run dev from a terminal. Then, launch the debugger with the "Launch extension without build" configuration. Whenever you change a code file, the whole extension will be rebuild to the out/ directory. You can reload the experimental instance of VS Code to reload the new version of the extension.

TODO

  • Get the debugger to work with F# code

    When setting breakpoints in F# code, the execution stops at the correct location, but the editor jumps to the transpiled JavaScript code. Breakpoints in ES2015 code, as seen in the src/formatter.js file, work correctly.