- Fixed some bugs with the latest version of VS Code
- Added support for reflecting changes to
window.title
in the title of the CodeSwing preview tab - Updated the default AI model to
gpt-4o
(which is much cheaper than Turbo) - Removed the logic that auto-adds
react
andreact-dom
to thescripts
arrow in yourcodeswing.json
file.
- Introduced the ability to generate and refine swings using an AI prompt (after configuring an OpenAI key)
- Fixed a bug in searching/adding modules to a JavaScript file
- Fixed a bug that prevented exporting swings to CodePen if they included an
in a file - Fixed some bugs with importing CSS files, and using React
- Markup files can now be named
main.*
in addition toApp.*
andindex.*
- Added experimental support for Go swings, which include a
main.go
file - Added a new
Go
template gallery, that is disabled by default
- Introduced a new
CodeSwing: Launch Behavior
setting, that allows customizing how CodeSwing should behave when you open a swing workspace. - Introduced a new
CodeSwing: Root Directory
setting, that allows specifying the workspace directory that new swings should be created in - Introduced a new
CodeSwing: Initialize Workspace as Swing
command, that allows you to open a folder and turn it into a swing - Added support for calling
window.open()
on HTTP(S) URLs - The swing library selector now properly filters out CommonJS/ESM modules and source maps when adding a JavaScript library
- The preview window is now automatically re-run when you upload a file to the active swing
- You can now use HTML in
index.md
files, when using Markdown as your markup format - Swings can now be open even when you don't have a workspace open
- Fixed a bug with using CodeSwing in Safari
- Fixed formatting of the tutorial navigation header
- Removed the timeout from tutorial step navigation
- Removed the
CodeSwing: Temp Directory
setting
- You can now
import
*.json
and*.css
files from a JavaScript module
- You can now
import
*.jsx
and*.tsx
files from a JavaScript module - Enabling "run on edit" for all file types
- Introduced the new
CodeSwing: Theme Preview
setting, which allows you to theme the swing preview window, to match your VS Code color theme
- Added support for React Native web 🚀
- Markup files/components can now be named
App.<extension>
in addition toindex.<extension>
- Introduced an MRU for templates, so that the last three templates you used show up at the top of the list
- Introduced a new
CodeSwing: New Swing from Last Template
command, that creates a swing from your last used template - Renamed the
CodeSwing: New Scratch Swing...
command toCodeSwing: New Swing...
, andCodeSwing: New Swing..
toCodeSwing: New Swing in Directory...
- Introduced a new
CodeSwing: Save Current Swing As...
command, that lets you save the current swing in a specific location - Added the
CodeSwing: Open Swing in New Window...
command
- File extensions can now be renamed and immediately edited (e.g.
.js
->.ts
,.css
->.scss
) - Fixed an issue with explicitly importing
react
from within a React component swing
- Supporting NPM imports in import'd files
- Being able to import Svelte/Vue components
- You can now use the
@import
and@use
statements in Sass files (file-based swings only) - Added the ability to upload local files to a swing
- Your
style.css
andscript.js
files can now be explicitly linked from yourindex.html
file, without breaking the run-on-type behavior.
- You can now add/rename/delete files from the CodeSwing tree (including files within sub-directories)
- NPM modules can now be
import
'd into React/Svelte/Vue components or script modules - Added support for using TypeScript and Scss/Sass within Svelte components
- Introduced support for React/Svelte/Vue component-based swings
- Added a keybinding for running a swing via
cmd+shift+b
(macOS/Linux) andctrl+shift+b
(Windows) - Fixed a bug with creating swings from a user-defined template
- Fixed a bug with tutorial navigation
- Optimized the extension to only activate when needed
- Added support for the
fetch
API, in addition to the existing support forXMLHttpRequest
- Introduced the
CodeSwing: Clear Console on Run
setting (defaults totrue
)
- Fixed a couple of bugs that impacted the swing experience on Windows
- The extension is now bundled with Webpack in order to improve peformance and reduce file size
- Added initial Live Share support for workspace swings
- Added support for exporting swings to CodePen via the new
CodeSwing: Export to CodePen
command - Added support for adding JavaScript module imports from Skypack
- Temporary swings were renamed to "scratch swings", and are now stored in the temp directory instead of in-memory, and you can configure the location to write them to
- Added the
CodeSwing: Open Workspace Swing
command, for re-opening the current workspace's swing after closing it.
- Changed the default value of the
CodeSwing: Readme Behavior
setting tonone
- Added support for auto-closing the side-bar when the opened workspace is a swing
- The panel area is now automatically closed when opening a new swing
Initial release 🚀