EXLcode is an open source, MIT-licensed, cloud+browser-based fork of the VS Code core maintained by EXL Inc.
Try it out at https://exlcode.com/
Get the Chrome extension here.
Read the user docs here
- GitHub integration (view and edit repositories and files, in place)
- Chrome extension for seamlessly using EXLcode in your daily workflow
- Complete project explorer and text editor
- Syntax highlighting and auto-complete for all major programming and markup languages
- IntelliSense for Javascript, TypeScript, JSON
- Project-wide search and replace
- Fuzzy filename search
- Side-by-side file comparison
- Themes
- Customizable Keyboard Shortcuts
- Per-user, per-project customizable editor settings
# Clone this repository.
git clone https://github.com/exlcode/exlcode
# Install npm packages
# Make sure that `which python` points to your installation python2 and that you have the build-essential package (on Ubuntu) for native builds and the xcode command line tools for OS X
# WHEN RUNNING ON A SERVER: For linux servers (no desktop), make sure you install X11 dev with `sudo apt-get install libx11-dev` otherwise the build will fail
# From the repo root, run:
./scripts/npm.sh install
cd ./exlcode
npm install
# Build
# From the repo root, run:
cd ./exlcode
npm run build
# Build targets:
# build - not minified, not optimized
# build-opt - packed not minimized. Requires ?b=opt when on localhost.
# build-min - packed and minimized. Requires ?b=min when on localhost.# From the root of the repo, run:
cd ./exlcode && npm run http-serverThe IDE will then be available at http://localhost:8000
If you are interested in fixing issues and contributing directly to the code base, you can setup your development environment following the steps above and check issues in this GitHub repo. Once your changes are ready, please submit a pull request in this repo for the team to review.
- Submit bugs and feature requests and help us verify as they are checked in
- Review source code changes
- Review the documentation and open issues/PRs for anything from typos to new content
Please leave your feedback and bug reports in our GitHub Issues.