CodeKit Changelog

What's new in CodeKit 3.27

Apr 18, 2024

ESLint Changes:
ESLint 9.0 drops support for the handy "environment" options (browser, jQuery, etc.) and instead makes YOU responsible for knowing what global variables are needed for a given environment.
That's dumb.
CodeKit has always been about getting rid of friction, so the environment options continue to work just as they always have—I simply reimplemented what ESLint dropped.
ESLint 9 also drops support for .eslintrc files, so those options have disappeared from the UI.

New in CodeKit 3.26 (Nov 8, 2023)

New in CodeKit 3.25 (Aug 28, 2023)

New in CodeKit 3.24 (Aug 8, 2023)

New in CodeKit 3.23.1 (Jun 20, 2023)

New in CodeKit 3.22 (Apr 18, 2023)

New in CodeKit 3.21 (Mar 13, 2023)

New in CodeKit 3.20 (Jan 12, 2023)

New in CodeKit 3.19 (Sep 22, 2022)

New in CodeKit 3.18.2 (Aug 24, 2022)

New in CodeKit 3.18.1 (Aug 8, 2022)

New in CodeKit 3.17.1 (May 6, 2022)

New in CodeKit 3.17 (May 5, 2022)

New in CodeKit 3.16.1 (Dec 29, 2021)

New in CodeKit 3.16 (Dec 22, 2021)

New in CodeKit 3.15.1 (Nov 19, 2021)

New in CodeKit 3.15 (Sep 17, 2021)

New in CodeKit 3.14.4 (Mar 19, 2021)

New in CodeKit 3.14.3 (Mar 4, 2021)

New in CodeKit 3.14.2 (Feb 16, 2021)

New in CodeKit 3.14.1 (Feb 16, 2021)

New in CodeKit 3.14.0 (Feb 16, 2021)

NEW TailwindCSS:
CodeKit now automatically supports TailwindCSS projects.
Use File > New TailwindCSS Project to spin one up fast.
Existing Tailwind projects are also supported from version 1.9.6+
For details, read the docs or watch the screencast.
NEW PurgeCSS:
PurgeCSS is now available for CSS, Sass, Less, and Stylus files.
It gets rid of unused CSS rules.
If you configure it incorrectly, it gets rid of all CSS rules.
Configure it correctly.
To do that, read the docs or watch the screencast.
If you email me, "CodeKit breaks my site!" and it turns out you forgot to configure PurgeCSS, I get to put a MIDI of my choice on your website for a month.
I have "MMMBop" in MIDI.
NEW CSSO:
CSSO is a highly-tuned CSS optimizer/minifier.
You can run it on CSS, Sass, Less, and Stylus files.
If you set the options just right, you can have PurgeCSS shoot you in one foot and CSSO shoot you in the other.
No, I will not share my "MMMBop" MIDI.
NEW Custom PostCSS Plugins:
CodeKit now honors your postcss.config.js file and runs any custom PostCSS plugins that you specify.
You can install PostCSS plugins from CodeKit's Packages area, like a civilized human.
There are important details about integrating your custom PostCSS plugins into the flow of plugins that are built into CodeKit.
You're fresh out of feet, so the next thing you're gonna shoot off is more valuable. Better read the docs or watch the screencast, Doc Holiday.
NEW CSS Imports:
You can now (optionally) have CodeKit combine all @import-ed files in a CSS file.
CSS files now show a "Linked Files" pane.
You can import CSS files in the same project, an npm package, or a CodeKit Framework.
Look, it's not important why I have an "MMMBop" MIDI.
NEW Build Environment Option:
There's a new "Environment" option in Project Settings > General.
You can now set certain tools (PurgeCSS, CSSO, Minifiers, Source Maps, etc.) to run only in a given environment.
The value from the PopUp Button is automatically synced with the NODE_ENV environment variable.
Big Changes:
CodeKit now runs natively on Apple Silicon.
Support for macOS 10.11 and 10.12 is dropped. Update your OS.
Other Changes:
More UI has been overhauled for Big Sur.
Rollup's "context" option is now exposed.
You can now select hidden folders in "Choose a Folder" panels.
The discontinued Neat framework no longer appears in the UI, but projects using it will still compile just fine.
Tool config files are now auto-ignored unless you explicitly change their Output Action.
The "strict math" option for Less files is removed because Less 4.0 no longer supports it.
The entire browser-refresh server was re-written using Swift-NIO. It's faster, better, thinner, sexier, multi-threaded...it's basically Tom Brady moving forward through time.
Fixed:
The cache buster generated different hashes for a file, even when the file's content had not changed.
The Packages list didn't sort correctly when reloaded.
Certain dependency links between Kit files weren't detected until a Project was refreshed.
Browser Refreshing might break if you used the back button in your browser.
Ugh, fiiiiiiiiiine.

New in CodeKit 3.13.3 (Oct 29, 2020)

New in CodeKit 3.13.2 (Oct 26, 2020)

New in CodeKit 3.12.1 (May 1, 2020)

New in CodeKit 3.12 (Apr 24, 2020)

New in CodeKit 3.11 (Apr 24, 2020)

New in CodeKit 3.10.2 (Oct 23, 2019)

NEW: The Kit @Compile Statement:
Works like @import, but compiles the file first.
Example: @compile 'someFile.md' will compile 'someFile.md' and drop the output in place.
Works with any file CodeKit supports, including custom file types you add to the app.
For details, watch this screencast or read the documentation.
NEW: Image Comparison Tool:
You know how every fall all the blogs are like, "The Pixel 67 clearly takes better photos than the iPhone 24 Pro Max. I mean, just look at my child's hair by candlelight. LOOK AT MY CHILD! LOOK AT IT!"
You know how those blogs have little sliders you can drag to compare the same photo from iPhone-whatsit and Android-dontcare?
That's now in CodeKit:
a screenshot of the image compare tool in CodeKit
If your Project uses a Build Folder (so the image doesn't overwrite itself when optimizing), you can instantly compare the original and optimized versions. Select the file and hit the space bar or double-click the preview thumbnail in the Inspector.
Other New Stuff:
Custom Environment Variables — Set them in the General section of Project Settings. They're available in all Hooks, Build Steps, and most of the tools CodeKit runs (including Babel, Rollup, etc.). See the documentation.
Libsass Globbing — Sass globbing is now supported when using the Libsass compiler. (Even multi-level globbing.)
Rollup Options — You can now specify external modules, enable/disable Treeshaking, and force string replacements when bundling. See the documentation.
Changed:
PNGQuant is now multi-threaded and optimizes large PNGs faster.
If you're still running macOS 10.11 or 10.12, you'll see a warning when CodeKit launches. Parts of the UI won't look right because of bugs in those ancient OS versions.
Fixed:
Output Paths weren't editable sometimes because Swift is a pedantic ass.
"Run Script" Build Steps sometimes failed if they appeared at the end of the Build process.
Links to ESLint rules in the Log didn't work because Swift is a pedantic ass.
Sass @debug statements weren't working due to a change in Libsass.
ESLint wasn't working for some people in the original 3.10 release.

New in CodeKit 3.10.1 (Oct 22, 2019)

NEW: The Kit @Compile Statement:
Works like @import, but compiles the file first.
Example: @compile 'someFile.md' will compile 'someFile.md' and drop the output in place.
Works with any file CodeKit supports, including custom file types you add to the app.
For details, watch this screencast or read the documentation.
NEW: Image Comparison Tool:
You know how every fall all the blogs are like, "The Pixel 67 clearly takes better photos than the iPhone 24 Pro Max. I mean, just look at my child's hair by candlelight. LOOK AT MY CHILD! LOOK AT IT!"
You know how those blogs have little sliders you can drag to compare the same photo from iPhone-whatsit and Android-dontcare?
That's now in CodeKit:
a screenshot of the image compare tool in CodeKit
If your Project uses a Build Folder (so the image doesn't overwrite itself when optimizing), you can instantly compare the original and optimized versions. Select the file and hit the space bar or double-click the preview thumbnail in the Inspector.
Other New Stuff:
Custom Environment Variables — Set them in the General section of Project Settings. They're available in all Hooks, Build Steps, and most of the tools CodeKit runs (including Babel, Rollup, etc.). See the documentation.
Libsass Globbing — Sass globbing is now supported when using the Libsass compiler. (Even multi-level globbing.)
Rollup Options — You can now specify external modules, enable/disable Treeshaking, and force string replacements when bundling. See the documentation.
Changed:
PNGQuant is now multi-threaded and optimizes large PNGs faster.
If you're still running macOS 10.11 or 10.12, you'll see a warning when CodeKit launches. Parts of the UI won't look right because of bugs in those ancient OS versions.
Fixed:
Output Paths weren't editable sometimes because Swift is a pedantic ass.
"Run Script" Build Steps sometimes failed if they appeared at the end of the Build process.
Links to ESLint rules in the Log didn't work because Swift is a pedantic ass.
Sass @debug statements weren't working due to a change in Libsass.
ESLint wasn't working for some people in the original 3.10 release.

New in CodeKit 3.9.2 (Jul 25, 2019)

3.9.2 fixes issues where TypeScript files failed to compile and npm packages with names shorter than 4 characters didn't show up in search results.
Quick Fix:
3.9.2 fixes issues where TypeScript files failed to compile and npm packages with names shorter than 4 characters didn't show up in search results.
NEW: npm!:
The 'Components' area of CodeKit has been 100% rebuilt from scratch.
It's WAY better. Faster, smoother, sexier. It's like Scarlett Johnasson, Ryan Reynolds, and Rachel McAdams had a sleepover with jQuery.
This is the nicest thing anyone has ever said about jQuery.
npm is now the default package manager.
The old UI was terrible. I'd say I can't believe you put up with that garbage, but you've probably got Slack's app running right now, don't you?
Bower is still fully supported. You can switch to it at any time, it uses the same new UI, and I even gave it new features. (Bower is deprecated by the developer, but it will be in CodeKit as long as it exists.)
There are SO many new features: uninstalling, pruning, viewing changelogs in one click, breaking/non-breaking update warnings, custom endpoint installations, installing from a package.json file...
Watch this 5-minute screencast to get up to speed fast. Or read the documentation.
NEW: Notification Control:
You can now control exactly when CodeKit posts notifications, beeps, and comes to the front.
See Preferences > Notifications
It was not possible to migrate your old options to this new system.
Other New Stuff:
Builds are 32% faster.
The log design has been tweaked. (It's not the sexy sleepover that the new npm interface is, but it's not Gary Busey either.)
Added the Babel UseBuiltIns and excludePaths options to the UI. (You can now control polyfills and transpile items in node_modules folders.)
New project icons.
The "Open With" menus now include Terminal as an option.
You can now force CodeKit to always reload the entire page, even when just CSS files change. (Useful for Shopify developers.) See Project Settings > Browser Refreshing
CodeKit is now notarized by Apple for security.
Changed:
CodeKit now attempts to keep its window the same size. Previously, when you switched sections, the app restored the last known size for that section.
CodeKit now supports full screen.
Windows are now much more fluid when resizing/animating.
Pages that do not have a or tag will now auto-refresh as long as they are HTML files.
Previously, CodeKit would use up to 8 CPU cores during builds. If your Mac has more than that, CodeKit will now use them all.
Fixed:
An issue where JS files with @codeKit statements wouldn't compile un-minified.
An issue where the Project Icon Picker wouldn't display icons sometimes.
An issue where browsers might hang and refuse to load the page if you switched the Preview Server from TLS to non-TLS.
macOS Catalina:
I don't officially support macOS betas, but folks tell me CodeKit is working fine on 10.15. This update is fully notarized and should be ready for Catalina.
Major Component Updates:
Autoprefixer 9.6.1
RollupJS 1.17.0
TerserJS 4.1.2
Babel 7.5.5
Libsass 3.6.1
Browserslist 4.6.6
TypeScript 3.5.3
ESLint 6.1.0
SVGO 1.3.0
HTML-Minifier 4.0.0
CoffeeScript 2.4.1
Node 10.16.0

New in CodeKit 3.9.1 (Jul 25, 2019)

3.9.1 fixes an issue in 3.9 where npm packages with names shorter than 4 characters didn't show up in search results.
NEW: npm!:
The 'Components' area of CodeKit has been 100% rebuilt from scratch.
It's WAY better. Faster, smoother, sexier. It's like Scarlett Johnasson, Ryan Reynolds, and Rachel McAdams had a sleepover with jQuery.
This is the nicest thing anyone has ever said about jQuery.
npm is now the default package manager.
The old UI was terrible. I'd say I can't believe you put up with that garbage, but you've probably got Slack's app running right now, don't you?
Bower is still fully supported. You can switch to it at any time, it uses the same new UI, and I even gave it new features. (Bower is deprecated by the developer, but it will be in CodeKit as long as it exists.)
There are SO many new features: uninstalling, pruning, viewing changelogs in one click, breaking/non-breaking update warnings, custom endpoint installations, installing from a package.json file...
Watch this 5-minute screencast to get up to speed fast. Or read the documentation.
NEW: Notification Control:
You can now control exactly when CodeKit posts notifications, beeps, and comes to the front.
See Preferences > Notifications
It was not possible to migrate your old options to this new system.
Other New Stuff:
Builds are 32% faster.
The log design has been tweaked. (It's not the sexy sleepover that the new npm interface is, but it's not Gary Busey either.)
Added the Babel UseBuiltIns and excludePaths options to the UI. (You can now control polyfills and transpile items in node_modules folders.)
New project icons.
The "Open With" menus now include Terminal as an option.
You can now force CodeKit to always reload the entire page, even when just CSS files change. (Useful for Shopify developers.) See Project Settings > Browser Refreshing
CodeKit is now notarized by Apple for security.
Changed:
CodeKit now attempts to keep its window the same size. Previously, when you switched sections, the app restored the last known size for that section.
CodeKit now supports full screen.
Windows are now much more fluid when resizing/animating.
Pages that do not have a or tag will now auto-refresh as long as they are HTML files.
Previously, CodeKit would use up to 8 CPU cores during builds. If your Mac has more than that, CodeKit will now use them all.
Fixed:
An issue where JS files with @codeKit statements wouldn't compile un-minified.
An issue where the Project Icon Picker wouldn't display icons sometimes.
An issue where browsers might hang and refuse to load the page if you switched the Preview Server from TLS to non-TLS.

New in CodeKit 3.8.2 (Mar 1, 2019)

New in CodeKit 3.8.1 (Feb 28, 2019)

New in CodeKit 3.8 (Feb 28, 2019)

New in CodeKit 3.7.4 (Oct 10, 2018)

New in CodeKit 3.7.3 (Sep 28, 2018)

New in CodeKit 3.7.2 (Sep 27, 2018)

New in CodeKit 3.7.1 (Sep 26, 2018)

New in CodeKit 3.7 (Sep 24, 2018)

New: Dark Mode + Mojave Support:
Dark mode is available on every version of macOS, not just Mojave.
On 10.14+, CodeKit will match the system accent color by default, but you can set a different one if you prefer.
Adopted Apple's new "runtime hardening" security. If the app is somehow ever compromised, this feature vastly limits what an attacker could access on your Mac.
New: Target Browsers:
A new category in Project Settings: Target Browsers
Shows all the desktop and mobile browsers in which your project will work.
Shows coverage percentages for the world and your local region.
Babel, Autoprefixer, and other tools will now automatically configure themselves based on what browsers you enter here.
New: Babel 7:
No more configuring. Babel will automatically choose the right plugins based on the browsers you support.
Much faster transpiling.
If you previously customized Babel settings, double-check them after updating.
New: Base64 Imports in Kit Files:
In Kit files, you can now write @import-base64 'someFile.png' to automatically base64-encode the target and include it in the base file.
See the Kit documentation for examples.
New: Less 3.0:
Less has been updated to 3.8.1 and some options have changed (mostly about when math operations get performed). If you use Less, double-check the options on your files after updating.
More:
The list of options for Syntax Checkers and UglifyJS is now searchable.
When ESLint shows an issue in the Log, you can now click the rule name to instantly adjust that rule in Project Settings.
New AppleScript command to process a single file at a time. See the docs.
The Preview Server now supports Content Security Policy (CSP) headers. If your site uses them, they just work; there's nothing to configure.
CodeKit now tracks@plugin directives in Less files and recompiles when they change.
The PNG image optimizer is about 10% faster.
Fixed:
If you add custom languages to the app, then swap extensions, settings don't get confused any more.
An edge-case where the preview server could crash.
A possible race-condition in browser syncing.
Triple-slash directives in TypeScript files weren't handled correctly.
CodeKit won't try to set up the refresh server on ancient browsers that can't handle it, which will make one guy stop emailing me.
Component Updates:
Libsass 3.5.4
Babel 7.1.0
Less 3.8.1
UglifyJS 3.4.9
CoffeeScript 2.3.1
Susy 3.0.5
MultiMarkdown 6.4.0
Autoprefixer 9.1.5
Haml 5.0.4
Bourbon 5.1.0
Bitters 1.8.0
Neat 3.0.0
ESLint 5.6.0
PNGQuant 2.12.0
Node 8.11.4

New in CodeKit 3.6.1 Build 26680 (Apr 10, 2018)

Take #2:
The people responsible for the original 3.6 release have been vigorously accelerated into the next plane of existence.
This release solves that release's problems.
The remaining people look highly motivated to get this one right.
Massively More Efficient:
CodeKit now uses 72% fewer CPU cycles to do the same amount of work. Better battery life, cooler laptops.
All processing tasks are also 11% faster, on average.
Folks still running macOS 10.12 get only part of the benefit, unfortunately. (See "Take #2", above.)
The Quiet Keyword:
You can now automatically silence warnings for imported JavaScript and CoffeeScript files using a keyword:
//@codekit-prepend quiet 'jquery.js';
(This is the same as unchecking the shield checkbox in the UI.)
Importing Skipped Items:
You can now use @codekit-prepend and @codekit-append statements to import any file on disk, even if it's in a Skipped Folder or outside of your project.
If a file can't be found for one of these statements, you'll get an error in the log. Previously, no error was reported and CodeKit just ignored the special comment.
More Good Stuff:
The progress bar now shows actual progress and is far more accurate during builds.
Builds can now be canceled.
Found a couple things in the UI that were not flat. Flattened them with extreme prejudice.
You can now choose "baseline" or "progressive" output formats for JPEG images.
Removed silent "Export Data To Russia" feature. Apparently that's now frowned upon.
Project Icons:
Fact #1: CodeKit has always used "apple-touch-icon" images as your Project Icon, if the image exists in a standard location when you add the project.
Fact #2: People put things in weird places.
Fact #3: CodeKit will now, by god, find your image. 84 levels deep in a folder named "not_NOT_porn"? I got you.
Fixed:
Optimizing JPEG files could discard their color profiles, causing them to look different.
Some images could be corrupted during optimization.
SVGO broke if a certain option was enabled.
Text in log entries could sometimes display all over the place.
Component Updates:Libsass 3.5.2
Ruby Sass 3.5.6
MultiMarkdown 6.3.2
CoffeeScript 2.2.4
SVGO 1.0.5
OptiPNG 0.7.7
Autoprefixer 8.2
Susy 3.0.3
TypeScript 2.6.2
ESLint 4.19.1
Node 8.11.1

New in CodeKit 3.5.2 Build 26330 (Mar 1, 2018)

New in CodeKit 3.5.1 Build 26268 (Feb 15, 2018)

New in CodeKit 3.5 Build 26261 (Jan 29, 2018)

New in CodeKit 3.4.2 Build 26148 (Nov 11, 2017)

A few things came up after 3.4 shipped on 31 October, so this update replaces that one and fixes:
An issue where the cache buster could crash on really short files.
An issue where Hooks failed to run on macOS 10.13.
Previewing in Blisk now actually previews in Blisk.
An issue with TypeScript imports and infinite loops.
An issue where syntax checkers hung.
New: Cache-Busting:
Automatic cache-busting is now available for all files that compile to HTML, all generic file types, and all custom languages.
It's smart. Caches are only busted when files have actually changed.
It's fast. And by "fast" I mean "instantaneous-thank-god-some-of-us-still-know-C"
Details: codekitapp.com/help/cache-buster/
New: Auto-Pause File-watching:
File-watching is now automatically paused whenever a version control app becomes active (Tower, Cornerstone, the GitHub app, etc.)
Optionally, you can also auto-pause file-watching when Terminal becomes active. To do so, choose CodeKit > Preferences from the menubar and check the box.
And there was much rejoicing.
New: CoffeeScript 2.0:
Fact 1: CoffeeScript now outputs ES2015, which means you'll need to transpile the output with Babel if you want to use it in a current browser.
Fact 2: CodeKit has Babel.
Fact 3: You don't need to do anything. There's a new "Transpile Output With" option for CoffeeScript files and it's automatically set to use Babel.
Fact 4: If you've customized Babel's options in your project, you MAY need to adjust those to get the CoffeeScript output you expect. (Basically, the ES2015 Babel preset needs to enabled.)
Fact 5: CodeKit just saved you, like, 3 hours of cursing and debugging a Gulp build script.
New: MultiMarkdown 6.0:
The MultiMarkdown compiler has been updated to version 6.
There are a few minor syntax tweaks, but it's unlikely you'll see any breaking changes.
It's much faster.
There's a whole host of new Output Formats available, including freaking eBooks. Seriously. You can now create an eBook complete with embedded images.
Changed:
If you have a "generic" file with an Output Action of "Process" but have not added a Hook to DO any processing for that type of file, the file will now simply be copied to its output path. Previously, nothing happened to it.
Clicking the "Files List" button when the Files List is already visible will now de-select all rows so that you can see the "Project Summary" pane again.
Jeet 7.2.0 has a couple minor mixin changes that may break your Sass. See the Jeet website for details.
Fixed:
A number of small drawing glitches on macOS 10.13 caused by the new Metal2 window server.
Control-clicking a group name in the Projects Popover did not show the contextual menu.
A rare edge case that could crash the app while scanning for @import statements in malformed files.
A race condition in the Preview Server that could cause a crash.
An issue where the CK_PROJECT_ROOT ENV variable was not set for "Run Script" Build Steps.
An issue where I hadn't given Apple any money in a while.
An issue where Bower may fail to install components with a 410 error.

New in CodeKit 3.4 Build 26097 (Nov 1, 2017)

New: Cache-Busting:
Automatic cache-busting is now available for all files that compile to HTML, all generic file types, and all custom languages.
It's smart. Caches are only busted when files have actually changed.
It's fast. And by "fast" I mean "instantaneous-thank-god-some-of-us-still-know-C"
Details: codekitapp.com/help/cache-buster/
New: Auto-Pause File-watching:
File-watching is now automatically paused whenever a version control app becomes active (Tower, Cornerstone, the GitHub app, etc.)
Optionally, you can also auto-pause file-watching when Terminal becomes active. To do so, choose CodeKit > Preferences from the menubar and check the box.
And there was much rejoicing.
New: CoffeeScript 2.0:
Fact 1: CoffeeScript now outputs ES2015, which means you'll need to transpile the output with Babel if you want to use it in a current browser.
Fact 2: CodeKit has Babel.
Fact 3: You don't need to do anything. There's a new "Transpile Output With" option for CoffeeScript files and it's automatically set to use Babel.
Fact 4: If you've customized Babel's options in your project, you MAY need to adjust those to get the CoffeeScript output you expect. (Basically, the ES2015 Babel preset needs to enabled.)
Fact 5: CodeKit just saved you, like, 3 hours of cursing and debugging a Gulp build script.
New: MultiMarkdown 6.0:
The MultiMarkdown compiler has been updated to version 6.
There are a few minor syntax tweaks, but it's unlikely you'll see any breaking changes.
It's much faster.
There's a whole host of new Output Formats available, including freaking eBooks. Seriously. You can now create an eBook complete with embedded images.
Changed:
If you have a "generic" file with an Output Action of "Process" but have not added a Hook to DO any processing for that type of file, the file will now simply be copied to its output path. Previously, nothing happened to it.
Clicking the "Files List" button when the Files List is already visible will now de-select all rows so that you can see the "Project Summary" pane again.
Jeet 7.2.0 has a couple minor mixin changes that may break your Sass. See the Jeet website for details.
Fixed:
A number of small drawing glitches on macOS 10.13 caused by the new Metal2 window server.
Control-clicking a group name in the Projects Popover did not show the contextual menu.
A rare edge case that could crash the app while scanning for @import statements in malformed files.
A race condition in the Preview Server that could cause a crash.
An issue where the CK_PROJECT_ROOT ENV variable was not set for "Run Script" Build Steps.
An issue where I hadn't given Apple any money in a while.
An issue where Bower may fail to install components with a 410 error.
Component Updates:
Bower 1.8.2
CoffeeScript 2.0.1
ESLint 4.9.0
Jeet 7.2.0
MultiMarkdown 6.2.2
Node 8.9.0

New in CodeKit 3.3 Build 25900 (Aug 21, 2017)

New in CodeKit 3.2 Build 25849 (Jun 21, 2017)

New in CodeKit 3.1 Build 25813 (Apr 5, 2017)

New in CodeKit 3.0.8 Build 25704 (Mar 11, 2017)

New in CodeKit 3.0.7 Build 25701 (Mar 10, 2017)

New in CodeKit 3.0.6 Build 25568 (Feb 23, 2017)

New in CodeKit 3.0.5 Build 25504 (Jan 18, 2017)

New in CodeKit 3.0.4 Build 25479 (Dec 14, 2016)

New in CodeKit 3.0.3 Build 25444 (Nov 4, 2016)

New in CodeKit 3.0.2 Build 25428 (Nov 2, 2016)

New in CodeKit 3.0.1 Build 25390 (Nov 2, 2016)

New in CodeKit 2.9.1 Build 19142 (Oct 20, 2016)

New in CodeKit 2.9 Build 19137 (Sep 22, 2016)

New in CodeKit 2.8 Build 19127 (May 10, 2016)

New in CodeKit 2.8 Build 19120 (May 10, 2016)

New in CodeKit 2.7.1 Build 19115 (Feb 11, 2016)

New in CodeKit 2.6.1 Build 19102 (Nov 20, 2015)

New in CodeKit 2.6 Build 19099 (Nov 20, 2015)

New in CodeKit 2.5.1 Build 19076 (Oct 16, 2015)

New in CodeKit 2.4 Build 19051 (Aug 10, 2015)

New in CodeKit 2.3.10 Build 19033 (May 27, 2015)

New in CodeKit 2.3.9 Build 19022 (May 22, 2015)

New in CodeKit 2.3.8 Build 18966 (May 6, 2015)

New in CodeKit 2.3.7 Build 18917 (Apr 30, 2015)

New in CodeKit 2.3.6 Build 18911 (Apr 29, 2015)

New in CodeKit 2.3.1 Build 18904 (Apr 28, 2015)

New in CodeKit 2.3.1 Build 18902 (Apr 27, 2015)

New in CodeKit 2.3 Build 18892 (Apr 25, 2015)

NEW: MultiMarkdown:
CodeKit has switched from the Discount Markdown compiler to MultiMarkdown!
This brings a ton of features for Markdown, including the ability to import MD files into each other.
If you use Markdown in CodeKit, you'll want to check the file's settings after updating; none of the old options exist any more.
For full details, see this help page.
NEW: JSON Language Support:
You can now minify and alphabetize JSON files.
This is opt-in; you have to turn on processing for JSON files in your project. By default, CodeKit won't do anything when you save a JSON file because most of them probably aren't meant to be processed.
For full details, see this help page.
NEW: Apple Watch Support:
Because of course Apple Watch Support.
Success messages will continue to be logged to the CodeKit window.
Error messages will now be logged only to your Apple Watch Edition.
The line number of the syntax error is indicated by haptic feedback. Simply count the number of pulses on your wrist.
Other Interesting Improvements:
The HTTP verbs DELETE and PUT are now supported. You'll still need an external server, but CodeKit will now proxy these requests correctly.
There is now an "Open With" command if you right-click a file in the list. Works like every "Open With" menu since the dawn of time.
Literate CoffeeScript is now fully supported. Note: you cannot combine *.litcoffee files with regular Coffee or JS files, but you can combine litcoffee files with each other.
You can now compile *.sass files with Libsass.
If your project has a 'bower.json' file, it should now be updated correctly when you install assets.
Hooks:
Bash Hooks can now get a list of all the files that CodeKit processed and created through the special environment variables CK_INPUT_PATHS and CK_OUTPUT_PATHS.
For full details, see this help page.
Stuff you probably don't care about:
The Inspector Panel is now scrollable. Lots of new options coming soon, so these had to go scrollable to fit everything I'm working on.
The Output Path section of the Inspector Panel has been tweaked for clarity.
Kayne West
Fixes:
Kit files in a subfolder of a CodeKit Framework were not found for import linking. That sucked. Let's not do that anymore.
TypeScript error messages stopped being displayed in the log. You make ONE joke about Bill Gates on Twitter, and suddenly all the Microsoft stuff stops working in your app.
If your DOM is really complex, Browser Sync could fire events on the wrong element. This is no longer the case.
Clicking 'Apply' while editing the AutoPrefixer Browser String in Project Settings will no longer discard your edits.
The 'Pause File-Watching' menu items now update their titles correctly when file-watching is, in fact, paused.
Component Updates:
Libsass --> 3.1 Beta 6 (TONS of fixes, including support for all output styles)
Sass --> 3.4.13
Less --> 2.5.0 (source maps now work with compressed output!)
Stylus --> 0.50.0
Autoprefixer --> 5.1.1
Uglify.js --> 2.4.20 (adds keep_fnames & bare-returns options)
CoffeeScript --> 1.9.2
CoffeeLint --> 1.9.4
JSHint --> 2.7 (adds futurehostile, varstmt & nocomma options)
Bourbon --> 4.2.2 (now the same version for both Ruby Sass and Libsass!)
Bourbon Neat --> 1.7.2
Bower --> 1.4.1
Node --> 0.12.2

New in CodeKit 2.2 Build 18493 (Jan 26, 2015)

NEW FEATURE: Browser Sync:
When previewing your website on multiple devices, whatever you do on one device is mirrored to all others.
It's pretty much magic.
You configure it in Preferences > Browsers.
It's ON by default, but if your network is not slow or congested, you should turn it off.
For full details, see this help page.
No, CodeKit does not use the Node.js BrowserSync project; this is totally custom.
Yes, I had to write some JavaScript to implement this and no, I'm not happy about it.
General Changes:
Files in CodeKit Frameworks can now import files in other CodeKit Frameworks. This is a terrible idea that's sure to end both your sanity and the human race, but some Guy wanted it.
The "default preview browser" preference has been moved from the General tab to the new Browsers tab.
You can choose the output format for Slim files: HTML, XHTML or XML.
CodeKit's browser injection script no longer pollutes the global scope with so many variables.
Fixes:
Sometimes, file output paths would magically change to root-relative paths (/Volumes/Macintosh HD/...) that were totally not correct. This was a terrible feature; it has been removed.
(It took a while because understanding the relationship between HFS+ filesystem paths and POSIX file system paths requires hallucinogens and a spirit guide.)
On some networks (especially VPNs), CodeKit would beachball while waiting for the network to return an address. F*** beachballs.
The Server Status was not displayed correctly when the server automatically restarts after your network connection changes. That no longer happens.
The "replace components" output path option would occasionally produce incorrect output paths. That no longer happens.
Hooks that run utilities installed in /usr/local/bin (like Grunt) will now work correctly.
The bundled version of Git is updated to 2.2.1 to close a zero-day exploit discovered in Git a couple weeks ago.
The entry for Modernizr in the Assets list is updated to reflect that project's new location.
TypeScript:
TypeScript's syntax is now fully supported.
The old way of combining TypeScript files (@codekit-prepend/append) has been removed.
After updating, you'll need to manually change your TypeScript files to use the official syntax; all existing links based on the old append/prepend statements will be destroyed.
Component Updates:
Libsass --> 3.1.0 (TONS of fixes)
Sass --> 3.4.10
Less --> 2.2.0
Compass --> 1.0.3
Autoprefixer --> 5.0
Uglify.js --> 2.4.16 (adds drop_console, pure_getters, keep_fargs & negate_iife options)
CoffeeLint --> 1.8.1 (adds spacing_after_commas, ensure_comprehensions & could_you_make_your_option_names_any_longer options)
JSHint --> 2.6
TypeScript --> 1.4.1
Jade --> 1.9.1
Bourbon --> 4.1.1 (for Ruby Sass) & 3.2.4 (for Libsass)
Bourbon Neat --> 1.7.1
Susy --> 2.2.1
Node --> 0.10.35

New in CodeKit 2.1.9 Build 18268 (Nov 11, 2014)

Compass Projects:
NEW: Autoprefixer and Bless are now (finally!) available in Compass projects.
NEW: Source Maps are now available in Compass projects.
CHANGED: the Output Style, Debug Style, Decimal Precision and Source Map options for Sass files in a Compass project are now configured in CodeKit's UI. The values for these options in the config.rb file will be ignored.
Output paths for Sass files in a Compass project must still be set in the config.rb file because Compass does not have an API that lets me override those.
Other items in the config.rb file such as required libraries, extra Ruby code to run, etc. are still honored. Only the "compiling options" have moved to CodeKit's UI.
For the reasoning behind these changes, see the help page.
NOTE: when you open existing Compass projects in this version of CodeKit for the first time, you must verify that the compiling settings in the UI are what you want them to be. They will not automatically match the settings in the project's config.rb file.
Libsass:
Libsass has been updated to version 3.0.2
This is a MASSIVE change that brings Libsass much closer to full Sass compatibility.
NOTE: if you use Zurb Foundation, you MUST update Foundation to the latest release (5.4.7). Older versions of Foundation do not support the current Sass syntax and will fail to compile. Use the 'Assets' tab in CodeKit to update Foundation.
General Changes:
OS X's Notification Center done got stupider in Yosemite. If more than about 8 notifications are posted in quick succession, it just shows nothing. (In Mavericks, they were combined into one notification.) This can lead you to believe that CodeKit is not working when, in fact, it is. This update addresses the problem by posting a single notification per group of files compiled rather than one notification for each file.
More safety checks: if the Ruby environment on your Mac encounters a problem that makes it unstable, this can no longer crash CodeKit.
Firefox Developer Edition is now available as a Preview Browser. And yes, that browser just came out today.
Fixes:
The Bonjour Preview Address is now more reliable on Yosemite.
Some text was blurry on Yosemite. That is no longer the case.
The oldest bug in CodeKit's history — intermittent overlapping text in the log view — has been fixed.
Clicking the preview button when CodeKit's internal server is not running will no longer cause a crash.
CodeKit's refresh script no longer uses function/variable names that could potentially conflict with names in your own JavaScript files.
Clicking "Open Website" on a Bower asset that has no website URL defined now shows an intelligent alert message.
The Server popover no longer erroneously reports the Internal Server as "stopped" when it's actually starting up for the first time after the app is launched.
Component Updates:
Sass --> 3.4.7
Stylus --> 0.49.3
JSHint --> 2.5.10
CoffeeLint --> 1.6.1
Bourbon Neat --> 1.7.0

New in CodeKit 2.1.8 Build 18027 (Oct 15, 2014)

New in CodeKit 2.1.7 Build 17945 (Oct 2, 2014)

New in CodeKit 2.1.6 Build 17908 (Sep 25, 2014)

NEW: You can now hide CodeKit's dock icon and use the app from the status bar only. Switch between the two states (or use both) without restarting the app. See the preferences window.
NEW: Added a global keyboard shortcut to toggle CodeKit's file-watching. Hit command + option + / in ANY app and CodeKit will ignore all changes in all projects until you hit the shortcut again. PERFECT for just before Git pulls/switches! (Pro-tip: to remember the shortcut, think of the slash as the // comment delimiter. Hit the two keys to the right of the spacebar, plus a comment.) The pause command is also available in the File menu.
NEW: include statements are now supported in Slim files. See the help page for details.
NEW: The project list can now be sorted alphabetically.
FIXED: Import links created via drag/drop will no longer be lost when you refresh a project or share it with teammates.
SECURITY: CodeKit now periodically verifies that its binary has not been tampered with. This is especially important if you use Hooks; you don't want a compromised app running random code on your Mac. Plus, the L33T H4XX0R5 from the torrent sites need something to keep them busy.
The File menu's "Preview in Browser" command now uses the browser you specify in Preferences rather than the system default.
The Status Bar menu has been expanded so that all app features are available when the dock icon is hidden.
Resolved several UI issues for Yosemite.
From this release onwards, if the app's data file was created by a newer version of CodeKit than the one you're running or if that file is corrupt, you'll see an option to perform a "safe start" when the app launches. Previously, you would see a cryptic "cannot initialize store" message.
The default Sass decimal precision for new projects has been increased from 5 to 10 digits. (Assuming you have not previously customized this yourself.)
Sass updated --> 3.4.5
Less updated --> 1.7.5
Stylus updated --> 0.49.0
Autoprefixer updated --> 3.1
Jeet updated --> 6.1.2
Jade updated --> 1.7.0
JSHint updated --> 2.5.6
Node.js updated --> 0.10.32
This release contains zero U2 albums.

New in CodeKit 2.1.5 Build 17756 (Sep 6, 2014)

New in CodeKit 2.1.4 Build 17753 (Sep 5, 2014)

New in CodeKit 2.1.3 Build 17682 (Jul 30, 2014)

New in CodeKit 2.1.2 Build 17670 (Jul 25, 2014)

New in CodeKit 2.1.1 Build 17625 (Jul 18, 2014)

New in CodeKit 2.1 Build 17580 (Jul 16, 2014)

NEW: The UI has been completely overhauled for Yosemite. I don't always redesign my apps. But when I do, I redesign them again four months after I launch.
NEW: Google Web Starter Kit is now built-in. See the help page for details.
NEW: You can now set all files of a given type to NOT generate output files by default. Open Project Settings, choose a language and see the Output Paths section. (Remember to click the "apply" button if you make changes; output paths for existing files do not change as you alter project settings.)
NEW: You can now set a default pattern to use for output filenames. Want all your Sass files to compile to "*-awesome.min.css"? Want your Kit files to compile to "*.php" instead of "*.html"? You can do that. Open Project Settings, choose a language and look in the Output Paths section.
CHANGED: Related to the last point, the much-hated "Javascript output suffix" option has been eliminated.
CHANGED: Pressing enter while typing in a Project Settings text field will deselect the text field and save your changes
CHANGED: The "installed" tab of the Assets area is much improved
CHANGED: When you save a file that is set to NOT create an output file, CodeKit will now reload your browsers. Previously, it did nothing
FIXED: The internal server now sets the correct Content-Type HTTP response header for all 983 file extensions recognized by Apache
FIXED: Text fields in the Project Settings area will no longer magically deselect themselves while you type
FIXED: Issue where setting an Uglify.js Reserved Names or Define string caused minification to fail
FIXED: Links on the "no index page" now work correctly once you navigate into a subfolder of that list
FIXED: Project icons with transparency now always draw with a white background
FIXED: An issue that caused Kit variable declarations to output extra newlines into compiled files
FIXED: False warnings about infinite import loops. This warning is now shown only when an actual infinite loop exists
FIXED: A crash triggered by dragging a folder with exactly 30 characters in its name onto the window. Programming is hard.
FIXED: An issue where the "replace X part of input path with Y" output path option incorrectly left the input file's name at the end of the path, leading to bad output paths.
Less updated: 1.7.3
Sass updated: 3.3.10
Libsass updated. No longer fails on !global declarations.
Stylus updated: 0.47.1
Slim updated: 2.0.3
Bourbon updated: 4.0.2 for Ruby Sass projects, 3.2.3 for projects using Libsass
JSLint updated: 8 July 2014 release
JSHint updated: 2.5.2
CoffeeLint updated: 1.5.2
Nib updated: 1.0.3
Susy updated: 2.1.2
Uglify.js updated: 2.0.14
Autoprefixer updated: 2.1
Note: Although the UI has been updated in preparation for Yosemite, you should NOT run CodeKit on OS 10.10 yet. There are several issues that will make your life difficult. These get fixed as Apple eliminates bugs in OS X so I don't worry about testing my apps until Apple ships a Release Candidate build.

New in CodeKit 2.0.6 Build 17018 (May 31, 2014)

NEW: click and hold (or click and drag) the Preview button to select a browser with which to view your project.
NEW: if your project has no index file, the page that CodeKit displays in your browser now has a directory listing so you can select something else.
CHANGED: The "Tools" menu has been renamed "Tasks"
NEW: under the Tasks menu, there is now a command to tell Git to use the https:// protocol instead of git:// when installing components. Use this if you're on a network that blocks the default port for git:// URLs (corporate networks, etc).
Auto-refreshing now works on pages that have tags outside of the element. (Wordpress is a big offender here.)
Note: putting link tags outside of the head element is a really bad idea because the browser has to restart its whole rendering process when it encounters the late tag.
FIXED: custom project icons now display properly in the Projects Sidebar.
FIXED: the no_unecessary_fat_arrows option on CoffeeLint now works correctly
FIXED: in Sass files, @import statements without quotes around the file path are now recognized properly.
FIXED: Chrome's Javascript console will no longer show a deprecation warning about Web Sockets.
FIXED: in the files list, icons no longer disappear when you select a row for a file that's imported into another file.
FIXED: in Kit files that use two variables in a line like this: href='http:///folder/, the second variable will now be handled correctly. Previously, it went unprocessed because no space/newline existed between special comments.
FIXED: the overlay that appears when you drag a folder onto the window now displays non-Latin characters correctly.
Note: as a result of the above, Kit variables can no longer contain the string "-->".
CHANGED: It's no longer possible to enable Libsass for *.sass files. (Libsass does not support Sass's indented syntax.) Had this feature been implemented sooner, the developer of CodeKit would not have wasted 25 minutes of his life trying to figure out why a damn Sass file wouldn't compile.
The Server popover has undergone a redesign in preparation for cool stuff to come.

New in CodeKit 2.0.5 Build 16921 (May 13, 2014)

New in CodeKit 2.0.4 Build 16903 (Apr 22, 2014)

New in CodeKit 2.0.3 Build 16895 (Mar 28, 2014)

New in CodeKit 2.0.2 Build 16877 (Mar 22, 2014)

New in CodeKit 2.0.1 Build 16844 (Mar 14, 2014)

New in CodeKit 2.0 Build 16828 (Mar 5, 2014)

New in CodeKit 1.9.3 Build 8403 (Nov 13, 2013)

New in CodeKit 1.9.2 Build 8376 (Oct 25, 2013)

New in CodeKit 1.9 Build 8348 (Oct 22, 2013)

MAVERICKS COMPATIBILITY. THREE KEY THINGS IN 10.9:
One --- it's no longer possible to run the app from only the menu bar. (10.9 changed the whole menu bar API to better support multiple screens, but that made it impossible for a single binary to reliably switch between Dock and Menu "modes".) There's a new option in the preferences to toggle the menu bar icon on and off and you no longer need to restart the app to do it. However, CodeKit will always show in the Dock. This also applies to 10.8 and 10.7.
Two --- CodeKit does not participate in "App Nap". You WANT CodeKit to stay alive in the background to listen for file changes. (I tested it with App Nap and found delays of up to six seconds between the time you pressed 'save' and the time OS X got around to allowing "napped" CodeKit to wake up and do something.) Luckily, CodeKit isn't very power-hungry to begin with.
Three --- The WebKit team procrastinates even more than me. WebKit nightlies, as of right now, do not run at all on 10.9. For technical reasons, this means that I cannot currently build a CodeKit binary that includes the code to auto-refresh the WebKit Nightly browser. So, for now, auto-refresh will no longer work for that browser on 10.9, 10.8 or 10.7. When the WebKit team gets their act together, I'll release another update that brings back auto-refresh for WebKit Nightlies. Also, WebKit team: Chrome Canary has been running on 10.9 for months. Just saying.
A certain Compass dependency was crashing on 10.9, so I removed it. Compass still works fine, but processing sprites may be a tad slower.
Sass updated to 3.2.12
Stylus updated to 0.38.0
Node updated to 0.10.21
JSHint updated to 2.3.0. New options: 'freeze' and 'notypeof'
Slim updated to 2.0.1
JSLint updated to the 22 Sept 2013 release
Jade updated to 0.35.0. (NOTE: if you want to use includes with Jade, you must install the relevant node packages at the command line. For example, to include Less code in your Jade files, you must install Less through NPM.)
FIXED: The "Run Bless" checkbox was accidentally removed from the Less options in the previous update. The people responsible for the previous update have been shot.