22 September 2018
Build 28795 — Download
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.
- 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.
- 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.
10 April 2018
Build 26680 — Download
- 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
- //@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.
- 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.
- 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.
|Ruby Sass ||3.5.6|
1 March 2018
Build 26330 — Download
NEW: Sortable, Searchable Log
- You can now filter the log to show only errors and warnings.
- Log results are now searchable by path, project name, or text in the result message itself.
- The log automatically switches back to "All Results" when a new build starts so you don't miss anything.
Zurb Foundation Update
- New Foundation projects now use npm instead of Bower to install components.
- Legacy Bower-based projects continue to work just fine.
- The new process is way faster and cleaner.
- I guess they named Gulp after what it does to your disk space. Should have called it Sip.
- An issue where some SVGO options failed to work correctly.
14 February 2018
Build 26268 — Download
Stuff And Things:
- Fixed: an issue introduced in the last update where the Kit language done got stupider.
- New: Autoprefixer option to add Internet Explorer prefixes for CSS Grid rules.
- Gitbox is now supported as a version control app for auto-pausing.
- You know who else updates CodeKit on Valentine's Day? Ryan Reynolds.
28 January 2018
Build 26261 — Download
New: Better TLS Support
- (TLS used to be called SSL. Hipsters decided too many people knew what it was, so new letters were required.)
- CodeKit previously supported TLS, but you would see warnings in your browser and it was finicky.
- This update provides TLS with no warnings. You even get the green lock icon in your URL bar.
- It's still just one click to enable, but you will need to send a certificate file to remote devices. Here's a quick screencast of how easy it is to do that.
- If your project uses an External Server and its address ends in .dev but does not start with https:// you'll now get a warning.
- (Google owns .dev and every major browser is now hard-coded to FORCE https:// for that domain.)
- An issue where auto-pause stopped working if you switched between Terminal and a Git app.
- In Kit files, an issue where special comments immediately following an @ character did not work.
- Fixed Meltdown and Spectre because everybody else was doing it.
- There are now some limitations on what you can enter in the "Build Folder" textfield, because somebody typed the wrong thing and wiped out all his files.
|Ruby Sass ||3.5.5|
10 November 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.
- 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.
- 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.
- 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.
17 August 2017
- The browsers Blisk and Vivaldi now appear in the Preview menu if they're installed.
- CodeKit now recognizes the Transclude Base metadata tag in MultiMarkdown files and will use it to correctly link imported files.
- If you hold the Option key while launching the app, CodeKit now asks before resetting all data.
- CodeKit now has Susy 3.0 built-in.
- 3.0 is the default version for all projects.
- For legacy Susy projects, switch back to version 2.0 in Project Settings > Frameworks > Susy.
- The SSL preview server is now working again in Chrome 59+. (It stopped working because Google changed their certificate parser.)
- An issue where trailing whitespace was incorrectly included as part of a variable value in Kit files.
- An issue where the Lannisters had an army.
- Slim files that import non-Slim files now show those links correctly.
- Custom Babel Presets now work correctly.
- An issue where Babel flipped out if the React node module is installed.
- If your Project folder contains a "." in its name, Output Paths were set incorrectly.
- ESLint options weren't applied correctly from New Project Defaults in some cases.
So...I've set a crazy goal to take CodeKit open source and make it free. More people will use it, other developers can help me improve it faster, etc. But I still have to pay bills, so I'll need help before I can do that. If you like me or my work, please see patreon.com/bdkjones for details.
|Bourbon ||5.0 Beta 8|
|JSLint ||8 August 2017|
20 June 2017
New: Local CSS Overrides
- You can now style and auto-refresh a website without hosting it locally.
- Great for complex sites that just HAVE to run on their live server.
- Watch this screencast for a quick walkthrough of how to use it.
- Whatever you do, however, do NOT watch this screencast.
- Issue where the "Preview Path Addition" option wasn't editable in Project Settings unless your project used an External Server.
- Issue where you hadn't seen the worst video on YouTube.
|JSLint ||10 April 2017|
5 April 2017
- This is the new, default PNG image optimizer in CodeKit.
- 70% smaller PNG files with virtually NO loss of visual quality.
- It's black magic. There's chanting involved. Virgins died. Souls were sold. (Mostly Kardashian souls though, so don't feel guilty.)
- While this is technically a "lossy" optimizer, it's the default one because it's THAT good. Trust me. Just re-optimize all your images.
- PNGQuant is written by Kornel Lesiński, the developer behind the fantastic Mac App, ImageOptim. He was kind enough to sell me a commercial license for the algorithm.
- See the PNG Help Page or the screencast narrated by Morgan Freeman for a walkthrough of the options.
- The old, lossless PNG optimizer (OptiPNG) is still available, if needed. See the docs for why you might use it on some images.
- I'm kidding, of course. Kardashians don't have souls.
If you saw a bouncing Dock icon during the last update, that was due to data migration. (When I add new options, the app has to apply them to existing items before it can run.) A little window was supposed to pop up with a message. It didn't. It does now. The migration process is also 85% faster.
- The preview server incorrectly added trailing slashes after URL query parameters in certain cases.
- Neat's main stylesheet was missing when you installed Neat in your project.
- Copying links by right-clicking "Documentation" buttons did not work.
- The "trial days remaining" banner did not disappear if you entered your license information manually instead of using the button in the license email.
- Projects set to auto-build newly-added items will no longer build those when the app first starts up. Items will only auto-build if CodeKit is running and watching the project in question when they are added.
10 March 2017
New: Lossy JPEG Optimization
- There's a slider in Project Settings > Languages > JPEG that lets you reduce image quality to get smaller JPEG files.
- You can also set quality on a file-by-file basis by selecting only JPEGs and using the right-hand Inspector panel.
- Remember: modern image editors are already *really* good at writing small files, so your gains may vary.
- Me: "Oh come on, you can't write a Sass file so complex it would cause a stack overflow in Libsass."
- You: "Hold my beer."
It is now literally impossible for an issue in Libsass to crash CodeKit. Malformed Sass files that previously crashed the app will now show correct error messages.
Libsass now runs as a completely separate process (codekit-libsass-service in Activity Monitor). The first Sass file you compile will take about one second longer while this process launches. All Sass files after that will compile without delay.
The built-in version of Neat has been upgraded to 2.0. You'll need to tweak a few things in your Sass files to use it. See this page for 1.8->2.0 changes.
- An issue where JPEG images sometimes failed to optimize.
- An issue in the 3.0.7 update that caused Sass compiling to fail on old versions of macOS.
22 February 2017
- By popular demand, the dock and menubar icons now show a "paused" symbol when CodeKit's file-watching is...wait for it...paused.
- You can now right-click the Dock icon to pause/resume file-watching.
- Libsass has gained support for @warn and @debug statements. You'll see them in the log when appropriate.
- Sorting Bower components by stars now starts with the components that have the most stars instead of the least.
- An issue where include statements in Slim files failed.
- An issue where browsers were sometimes unnecessarily refreshed twice.
- If you closed the New Project Defaults area while a text field was still editing, the new value wasn't saved. It now is.
- An issue where Susy did not work correctly with the Libsass compiler because I forgot a colon in a string. No, really; one colon. This is why developers drink.
- An issue where Compass reported (null) for error messages instead of the actual error message.
- For a variety of dubious technical reasons, the Browser Refresh Delay value is now limited to integers between one and six seconds.
|Libsass ||3.5.0 B3|
17 January 2017
- An issue where Slim files compiled into nonsense.
- An issue where variables in Kit files that started with capital 'A' through capital 'N' were not detected correctly. The issue was addressed by sending the people who began variable names with capital letters to re-education camps.
- An issue that caused CodeKit to rewrite URLs in assets other than webpages (such as JS files) when using an external server.
- An issue where Mariah Carey still had a career. The issue was addressed through additional public humiliation.
- Hooks can use a new environment variable to access the current project's root folder: $CK_PROJECT_ROOT. This is in preparation for a big new feature in the next release.
- #teasing #stillnotanewmacpro
Jeet is being maintained again! This release includes Jeet 7, which has a few breaking changes. Read the migration guide. (Ignore the crap about updating import statements though. You use CodeKit, so just write @import 'jeet'; and go.)
|Ruby Sass ||3.4.23|
|JSLint ||10 January 2017 Release|
14 December 2016
- SVGO options were not applied correctly, causing SVGs to not optimize correctly.
- Text in the log mangled itself when selected.
- An issue where changes to an output file did not trigger re-compiling of files that import that output file.
- A rare memory corruption issue when restarting the preview server.
- An error when using Slim's "logicless" mode.
- An issue where Autoprefixer and Bless options from Project Settings weren't applied correctly to stylesheet files.
- JS files that are set to not minify or transpile now get written to their output path as-is when processed.
- Entries in a "Process Items" build step now maintain their order to avoid Git conflicts in the config.codekit3 file.
- An issue where the world was likely to prosper for the next four years.
3 November 2016
- This update includes Bourbon 5.0.0 Beta 7
- Some mixins have been removed, some have been updated. You may need to tweak your Sass. For details, see the Bourbon Changelog.
- An issue where installing Bitters files failed because CodeKit was being dumb.
- An issue where SVG optimization silently failed if the output folder did not exist.
- Enabling WordPress debugging mode no longer puts your browser into a reload loop.
- A small memory leak in the Kit compiler
- An issue where I almost went three days without releasing an update.
|Bourbon ||5.0.0 Beta 7|
1 November 2016
- If you select a folder that is NOT skipped, you can now set the Output Action for all items in and below that folder at once.
- Useful if, for example, you want to set everything in bower_components to "ignore", but don't want to skip the folder so that you can still do things like prepend JS files that are in that folder.
Trailing Slash Behavior:
- If you type an address in your browser like http://vdk.local:5757/subfolder and omit the trailing slash, CodeKit will now redirect the browser to the URL with a trailing slash.
- This happens as long as the directory you requested (here, "subfolder") actually exists. If it does not, the server returns a 404. (Because you *could* be requesting a file that has no extension, so the server can't assume that the resource you requested is supposed to be a directory.)
- Custom Bower Favorites weren't loaded correctly.
- Code pasted into a Hook or Build Script textView did not save correctly.
- If you added a "Preview Start Path" in Project Settings, the non-Bonjour server address incorrectly showed the Bonjour address.
- An issue where the developer of CodeKit was not caught up on The Walking Dead.
- Scanning CoffeeScript files with CoffeeLint produced a crash. Ain't nobody got time for that nonsense.
- JSHint options got cut off in Project Settings.
- .codekit-cache folders no longer show up in the files list.
- The search field in the files list Scope Popover did not clear correctly in some cases.
- Fixed a few outdated option strings for ESLint options.
- Three beta testers were sacrificed to Ba'al, The Soul-Eater. This was done to ward off future bugs, but since none of them were virgins, Ba'al was displeased. I would back up your Mac.
29 October 2016
Apple and I released new stuff together. There were a couple bugs in CodeKit, so that's a point for Apple. But...you don't have to take out a second mortgage on your house to buy dongles when you upgrade to CodeKit 3. So that's a point for CodeKit. See you at WWDC, Schiller.
- Hidden items like .htaccess files now appear in the list so they can be processed/copied on build.
- Menu command and keyboard shortcut to open the Build area: cmd+5
- An issue where New Project Defaults were not applied correctly for syntax checkers, UglifyJS and Babel.
- An issue where default output path options were not saved correctly for the Kit language.
- Files that do not have an extension no longer have a dangling period at the end of their output paths.
- The link to Haml's documentation was incorrect.
- An issue where extra newlines were added to a JS file in certain cases.
- An issue where a log message could be blank if a file was processed but there was nothing to do.
- An issue where none of my 80 beta testers caught any of this stuff and were allowed to retain full use of their legs.
26 October 2016
Is It Perfect?
Nope. I'm sure there are some bugs that got past the beta.
Is It Going To Explode And Set A Plane On Fire?
No. The bar for success has really been lowered.
20 October 2016
Build 19142 — Download
This update adds a few things that will enable a seamless migration to CodeKit 3, which is launching next week. Skipping or procrastinating on this update is a poor life decision.
20 September 2016
Wait, You're Still Alive?
- Neither myself nor CodeKit has been George-R-R-Martined.
- More on that after a word from our sponsor.
My thanks to Squarespace for sponsoring this episode of my release notes. I have no idea why they decided to be a sponsor—you guys build stunning websites by hand; seems like you don't need Squarespace. ...Maybe their ad department was drunk? Anyway, Squarespace: build it beautiful.*
Where Have You Been?
- Buried in Xcode. And as a result, I'm happy to announce that this is likely the very last release of CodeKit 2.x
- Put down the pitchfork; I have something better:
- Before Apple ships new Macs, that's for sure.
- I'm finishing up a couple edge-cases around transpiling JS files. (Transpiling JS files ALWAYS has more edge cases.) Then I have to update the Help pages and record some screencasts.
What's The Upgrade Story?
- If you own a 2.0 license, you install 3.0 and every single feature that was part of 2.0 stays unlocked. Forever. For free.
- That's why this is the last 2.x release: you can install and use CodeKit 3.0 without paying anything. You even get the swanky new UI, a 2,500% speed increase and a bunch of little features I'm too lazy to lock. Free. No banners, no upgrade prompts. Just a nice, clean app.
- When you decide all the new 3.0 features are worth it, upgrade your license at a huge discount and they're yours.
- Oh, and the migration is seamless. Drop a 2.x project on 3.0 and all your settings come across. All your preferences and New Project Defaults come across on first-run, too.
- And, of course, if you buy a 2.x license now, you'll get a free 3.x license.
So What's In 2.9?
This update provides stability on macOS Sierra. And fixes a few bugs by updating components.
|JSLint ||31 August 2016 Release|
*I listen to too many podcasts. Squarespace is not actually a sponsor
10 May 2016
- Safari Technology Preview is now an option for the Preview Browser.
- Hired Ramsay Bolton to deliver my totally constructive, friendly, and 100% positive feedback to Apple Developer Relations.
You may need to change the Output Module type for your TypeScript files from CommonJS to System after this update, due to a change in the TypeScript compiler.
11 February 2016
Build 19115 — Download
This is the last release of CodeKit that runs correctly on OS X Yosemite, OS X Mavericks, and OS X Mountain Lion. If you are still running any of those ancient OS's, update your Mac and then install CodeKit 3.
CodeKit uses the open-source Sparkle framework to manage updates. Last week, a large man-in-the-middle vulnerability was found in Sparkle. Prior releases of CodeKit should be unaffected because all updates are delivered over SSL. Nevertheless, this release includes a new, fixed version of Sparkle (1.13.1).
The original CodeKit 2.7 release contained Libsass 3.3.3, which had a critical regression that broke Sass compiling for many people. Version 2.7.1 returns to Libsass 3.3.2 until the Libsass team fixes the problem. Ask me how many emails I've gotten in the last 5 hours.
|JSLint ||7 February 2016 Release|
20 November 2015
- Foundation 6, which launched today, is now built in!
- Installing it is super complicated: File > New Foundation Project
- The old Foundation 5 templates are still available, but you should not use them. They're "soft-deprecated" by Zurb. Version 6 is way better.
This update brings Libsass to 99% feature parity with the Ruby Sass compiler. It contains hundreds of fixes and makes Libsass about 50% faster than it already was. If you're not using Libsass at this point, you're doing it wrong.
- An issue where OS X incorrectly reported CodeKit as damaged and unable to run for some users.
- An issue introduced in version 2.6 where Nib did not work with Stylus.
- An issue introduced in version 2.6 where the Sass-globbing plugin went nuts.
- An issue where The Walking Dead writers maybe killed a major character at the end of an episode, then did not reveal his fate in the next episode or the episode after that and the writers themselves were not killed.
|Markdown ||MultiMarkdown 5.0|
|JSLint ||20 October 2015 Release|
16 October 2015
- On El Capitan, dragging a folder onto the window would not work in some instances. It now does.
- In BBEdit, certain file icons caused choppy scrolling. That is no longer the case.
- When setting an output path for a file, the path sometimes erroneously re-started at /Users/ if your filesystem had corruption. This will no longer happen. Apple fixed the corruption issue in 10.11, so this affects only those on 10.10 and below.
- An issue where certain http downloads were rejected on El Capitan.
- An issue where Autoprefixer whined about something being deprecated.
- In some edge cases, sending Matt Damon into space results in unpredictable behavior. This update addresses the issue by no longer sending Matt Damon into space.
This release brings TypeScript 1.6.2, which is notable for a few reasons:
- TypeScript now supports JSX and React with the new *.tsx file extension.
- There are two new options: Module Resolution and JSX Handling. If you work with TypeScript, you should check the docs and make sure these are set correctly for your project.
- There are some backwards-incompatible changes. Read the TypeScript blog for more information.
|Node ||Not 4.0 because Aaron said it breaks stuff.|
10 August 2015
A nice little maintenance update for the dog days of summer.
- Variables in Kit files can now be set to nil: <!-- $myVar = nil -->
- When nil, a variable is essentially a no-op; nothing is put in its place in the final HTML output.
- It's still an error to have undefined variables; they must be something or nil.
- This makes it easy to do stuff like active classes on nav menu items, etc.
Doug Crockford recently overhauled JSLint to be less Donald Trump-ish. Most of the old options are gone and only a few remain. This release includes the new JSLint and you might actually like it because it will no longer find 4,567 errors in a 25-line file.
26 May 2015
- CodeKit now reports anonymous analytics such as which version of the app and OS X you're running.
- You can turn this off in Preferences and I will never collect any identifying information.
- This data will help me make better decisions about the app, like when I can drop support for Mavericks (soon).
- Plus, the hipsters won't let you into any of the cool bars in San Francisco if you don't have analytics.
Fixes and Changes
- Fixed: an issue introduced in 2.3.9 where certain config.codekit files could crash the app.
- The FSEvents fix is even more refined.
21 May 2015
The FSEvents bug is DEAD.
- What this means: auto-compiling will never stop working again.
- Apple's proposed fix in the last update did not work.
- Fortunately, a bunch of people working together found a workaround that DOES fix this OS X bug.
- Andrey Tarantsov deserves a huge thanks for writing the actual workaround. And an Apple Engineer named Kevin Elliott gave me the critical info we needed to write that workaround.
- The "Remove Whitespace" output style for Less files is no longer supported by the Less compiler. It has been removed. Files that used this setting will automatically be set to Compressed output.
- Libsass has been updated to version 16.7.1, which will be released in November, 2028.
- To get this, I had to send Matthew McConaughey through a blackhole. He missed his daughter's entire life. I hope you're happy, Libsass. This is what happens when you try to update more frequently than me.
- To preserve the stability of the spacetime-continuum, the About Window refers to this version as Libsass 3.2.4
5 May 2015
The FSEvents Bug: Killed. Maybe.
So you know how CodeKit sometimes can't see file-changes because of a bug in Apple's FSEvents API? I've spent five days discussing this with Apple Engineering. They've given me a fix, but they're not completely sure it's going to work. (So...kinda like WiFi in Yosemite.) This update has the fix in it.
If you still find a folder that's not responding to file-changes, quit and relaunch CodeKit. If that doesn't fix it, please contact me so I can
berate tell Apple.
- The Assets area has been tweaked to show more information about components
- You can now search by the git:// address of a component, as well as by owner, URL, keyword, name and description.
- The 'All Components' tab now lists literally every component you can possibly install with Bower—dead or alive. Some of the ones that 404 are actually, magically, still installable. (Previously, I pruned the 404-ed components.)
- You'll see lightning bolts next to some components. These are components that are registered with Bower, but are NOT in the online search results at bower.io/search. Many of these components are dead and will fail to install. Many are not. Good luck!
- Compiling a Sass file with lots of warnings could cause the Compass compiler to hang and never finish. This is no longer true.
This update includes Libsass 3.2.2, which was released 15 hours after CodeKit 2.3.7 which was released 15 hours after Libsass 3.2.1 which was released 15 hours after CodeKit 3.2.6 which was released 15 hours after Libsass 3.2. See you in 15 hours.
And, of course, there's STILL all the stuff from those three updates last week:
29 April 2015
- The Libsass team released an update to the update they released yesterday.
- It has some really important fixes, including one for @import url(...) problems introduced in Libsass 3.2
- The CodeKit team released an update to the update they released yesterday to the update they released the day before that.
- *Cracks Knuckles* Bring it, Libsass. This isn't the Mac App Store; I can do this all week.
This update also brings support for refreshing stylesheets that are included through HTML5 Imports and makes browser refreshing compatible with WebComponentsJS's ShadowDOM Polyfills.
And, of course, there's STILL all the stuff from the 2.3.6 and 2.3.1 updates, 48 hours ago:
28 April 2015
- Large projects now refresh about 73% faster.
- My example project has 9,500 files. It used to take 15.1 seconds to refresh. It now takes 3.9.
- The Libsass team released the final version of Libsass 3.2 about 15 hours after my last update.
- I released a new version of CodeKit about 15 hours after the Libsass team's last update.
- Your move, Libsass.
And, of course, there's all the stuff from the 2.3.1 update, yesterday:
27 April 2015
- 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.
- 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
- 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.
|Libsass ||3.1 Beta 6|
|Bourbon Neat ||1.7.2|
After releasing 2.3 on Friday, some folks pointed out some bugs that I needed to fix quickly:
- The Sass Decimal Precision dropdown in Project Settings now works again.
- The "check for updates" command no longer worked correctly
- Libsass always generated source maps, even when you turned them off.
24 January 2015
Here's what I've been working on for the past two months:
NEW: 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 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.
- 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.
- 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's <reference path='...' /> 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.
|Bourbon ||4.1.1 (Ruby Sass) and 3.2.4 (Libsass)|
|Bourbon Neat ||1.7.1|
10 November 2014
This is a huge release with lots of changes. Let's break them down by section.
- 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 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.
- 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.
- 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.
- 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.
|Bourbon Neat ||1.7.0|
- Everyone who installs this update between now and December will be automatically entered to win Drew Wilson's new Retina 5K iMac.
- It would be best if we did not tell Drew about this.
18 October 2014
I'm re-releasing 2.1.8 to correct an issue where include statements did not work with Slim 2.1 and an issue where Frameworks did not remember settings. Plus, there's now a CodeKit plugin for Sublime Text available. Was there a bug in the original 2.1.8 release? Yes. Did it stop 40,000 iPhone 6's from making phone calls? No. We'll mark that a win.
Original 2.1.8 Changes
- NEW: CodeKit now supports AppleScript! This enables editor plugins like the one below. See https://codekitapp.com/help/applescript/ for examples and details.
- CHANGED: CodeKit now reloads stylesheets of all media types. Previously, any stylesheet containing a print type was skipped.
- CHANGED: Support for the latest version of Google Web Starter Kit
- FIXED: Scroll position is now restored only when a full-page reload occurs. Previously, scroll position was incorrectly set while navigating links.
- FIXED: an issue that made it impossible to re-select "none" for "Debug Style" while inspecting a Sass file
- FIXED: the bower_components subpath is now settable as a new-project-default
- FIXED: an edge-case potential crash if a folder's name matched an expected file's name (e.g. "_main.scss")
- FIXED: an issue where files in disabled frameworks incorrectly appeared in "linked files" lists
- More Yosemite refinements, including support for dark menubar mode
|Bourbon Neat ||1.7.0rc|
Use Coda? Me too. Wish Coda would automatically launch CodeKit and add projects to the app as needed? Me too. So I made that happen. Download the new CodeKit Plugin For Coda and CodeKit will automatically launch itself and add project folders in the background as you work in Coda.
Use a different editor? Check out the new AppleScript APIs and the Coda Plugin Source Code to see how I did it. Make a plugin for your editor of choice and email me so I can feature it! Also: first person to find a bug in my source code wins a free CodeKit license. First person to email me about how if statements should have braces on the same line and I should really be using tabs instead of spaces...wins a 4,389 word email about proper coding style.
Keep using Libsass to compile Sass files in a Zurb Foundation project because the latest Ruby Sass compiler (3.4.5) is not yet supported by Foundation. This should clear up in the next few weeks. See the link in the 2.1.7 release notes, below, for more information.
2 October 2014
- The default global shortcut to toggle file-watching is now command + option + control + /. (It's the three keys to the left of the spacebar plus a forward slash like a // comment.) The previous default shortcut conflicted with several IDEs.
- You can now customize this shortcut in the preferences window.
- FIXED: An issue introduced in the last update that broke drag/drop links between CoffeeScript files.
- FIXED: CoffeeLint settings are now recorded correctly in the config.codekit file, so they'll stick around.
- FIXED: An issue that could cause CodeKit to bend if run from your pocket.
If you use Zurb Foundation, you need to read this thread about the current state of Sass: https://github.com/bdkjones/codekit2/issues/443. There are a few edits you need to make to the Compass config.rb file after creating a new Foundation project in CodeKit or it won't compile. If you use Libsass to compile your Sass files, you're unaffected.
TL;DR --> Use Libsass to compile Sass files in Foundation projects until you see an 'all clear' message here.
24 September 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 + control + / 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.)
- This release contains zero U2 albums.
5 September 2014
- Sass updated to 3.4.3 (which was released yesterday, right after the CodeKit update). This resolves several bugs in Sass.
- WARNING: The current release of Zurb Foundation is broken when compiling with Sass 3.4+. Fortunately, the fix is very easy. See this thread for the one-line change to make.
- Sass deprecated the old behavior back at the start of 2014 but Zurb still hasn't updated their code.
- In related news, I nominate the Zurb Foundation team for the ALS Ice Bucket Challenge.
4 September 2014
- NEW: Source maps are now available for Stylus.
- NEW: Jeet (a cool grid system that supports both Sass and Stylus) is now built-in. See the help page for details. Or just add @import 'jeet'; to the top of your stylesheet.
- CHANGED: "node_modules" folders are now skipped by default for new projects
- CHANGED: separator comments have been removed from concatenated JS and Coffee files
- CHANGED: the live-reloading script is now inlined in <head>. This makes the preview server a hair faster and eliminates an issue for one guy who is quite the persistent emailer.
- FIXED: under rare conditions, an import statement in a *.sass file that targets a *.scss file was not detected correctly.
- FIXED: links on the "no index page" now properly strip query parameters from their URLs so that the links actually work.
- The update-checker has been updated.
- Bower has been updated to 1.3.9, resolving several edge-case issues installing assets
|Bourbon Neat ||1.7.0pre|
30 July 2014
- FIXED: Excessive "Could Not Start HTTP Server" alerts no longer appear. When your network connection status changes (e.g. your Mac goes to sleep), the server now updates without restarting itself.
- FIXED: Android and Windows devices no longer infinitely refresh every 5 seconds.
- NOT FIXED: Some of you use Android.
- CHANGED: The self-healing feature introduced in the last update has been removed. See the discussion below.
I tested the self-healing feature on a strong, fast WiFi network. If your WiFi is laggy (e.g. a public network), the self-healing routine would repeatedly try to reconnect to CodeKit because the HTML5 websocket protocol has no way to determine if a connection is truly dead or just laggy. In version 2.1.3+, if a page loses touch with CodeKit for 15+ seconds, it will display a banner telling you that the connection is unstable, but it will NOT attempt to automatically reconnect, since the connection may not be dead.
Auto-refresh on remote devices really requires a solid, fast WiFi network to work well. If the network is bogged down with traffic or you're at the edge of the router's signal range, refreshes will probably be slow and/or unreliable.
24 July 2014
- NEW: Connections between your devices and CodeKit are now self-healing. When a device loses contact with CodeKit, it will try to reconnect every 5 seconds automatically.
- FIXED: Browsers on your Mac will continue working with CodeKit's refresh server no matter what happens to your network connection now.
- FIXED: An issue where files with names like someSass.sass would handle the file extension incorrectly if you omitted it in an @import statement because the extension was also the last part of the file name.
- Better error messages when Foundation, Bower components and Web Starter Kit fail to download correctly.
- More fixes for those of you who will try to run CodeKit on the Yosemite Public Beta. You know who you are.
18 July 2014
- NEW: @import globbing is now fully supported for Sass, Compass and Stylus files. Writing @import "someFolder/*" will cause all relevant files in that folder to be imported in alphabetical order. CodeKit will correctly mark them as imported and recompile the base file when they change.
- NOTE: Libsass does not support globbing. "Tree globbing" (i.e. writing @import "someFolder/**/*"; to import all files in all subfolders of 'someFolder') is NOT supported anywhere because that's how the world ends.
- FIXED: UglifyJS updated to 2.4.15 to resolve an issue that prevented source maps from being written correctly.
- FIXED: You can now add Hooks in the New Project Defaults area and those Hooks will automatically be added to brand new projects from then on.
- FIXED: The Google Web Starter Kit link now actually works.
- FIXED: If you import files with periods in their names like @import "somefile.colors"; and omit the extension (because you like to live dangerously), CodeKit will now try to guess what you meant and link files correctly, instead of assuming '.colors' is the extension. (If you use file names with dots in them, you should never omit the extension.)
- FIXED: Deleting the config.codekit file in a project while it's in CodeKit will no longer cause that project's settings to warp back to your New Project Default values.
15 July 2014
For lo, on the sixth day St. Ive descended from on high and said unto the masses, "Abandon thy wicked ways my brothers and sisters. Let not thy elements have bevel nor depth nor gradient. Walk not in the drop shadows of thy forebearers, but be flat and translucent in all thy ways that you may know paradise." And the masses rejoiced except one man who said unto St. Ive, "But does not translucency distract, my lord? Surely it is wasteful and ornamental!" And St. Ive looked upon the man and the man was no more.
- 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: 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 UglifyJS 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.
|Libsass ||No longer fails on !global declarations|
|Bourbon ||4.0.2 (Ruby Sass) 3.2.3 (Libsass)|
|JSLint ||8 July 2014 Release|
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.
30 May 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 <link> tags outside of the <head> 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 <link> 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: 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://<!--$someVar-->/folder/<!--$otherVar-->, 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.
12 May 2014
- NEW: Custom project icons. If your project has 'apple-touch-icon.png', '/images/apple-touch-icon.png' or 'img/apple-touch-icon.png', that image will be the icon when you add the project to CodeKit for the first time. For existing projects, right-click any image in the file list to set it as the icon.
- FIXED: Edge-case issue when using an external server for a project that could break browser-refreshing.
- FIXED: Hooks will no longer cause crashes on OS 10.8.5.
- FIXED: The "conditions" editor in the Hooks section of the Project Settings area now always shows friendly text descriptions.
- Sass updated to 3.3.7
- Stylus updated to 0.44.0
- JSHint updated to 2.5.0 (Several options were removed, including the one about trailing whitespace.)
- JSLint updated to 21 April 2014 release
- Bourbon updated to version 4.0.1
- WARNING: Bourbon 4 uses Sass 3.3+ syntax. This means Libsass will NOT work with Bourbon 4+ (yet). Normally, this would make your life difficult. But this isn't "Steve's Shady Mac App" (a.k.a. "Messages"); this is CodeKit. The app will automatically use Bourbon 3.2.1 if your Sass file is set to compile with Libsass.
- WARNING: The above means that if you use Bourbon with Libsass, you need to reference the 3.2.1 Bourbon docs! Also, if you install Bourbon 4's files in your project, you can't use Libsass to compile them.
- Bourbon Neat updated to 1.5.1. This version has feature-parity with Neat 1.6, but is compatible with older Sass syntax (and therefore Libsass).
- CoffeeLint updated to 1.3. New options added.
- TypeScript updated to 1.0.1.
19 April 2014
The Starks send their regards.
- Susy 2 is now built-in. If you have existing projects that use Susy 1.x, you need to change the @import 'susy'; statement to @import 'susyone'; to continue working with Susy's 1.x syntax.
- Sass updated to 3.3.5
- Stylus updated to 0.43.1
- @require statements are now recognized in Stylus files.
- Uglify.js updated to 2.4.13
- Jade updated to 1.3.1
- Node.js updated to 0.10.26
- Libsass updated to the latest commit from the GitHub repo.
28 March 2014
First new feature since the 2.0 launch plus some bug fixes.
- New: You can now choose which browser opens when you click 'Preview'. See the Preferences area.
- Fixed: If you set an output path for a file that is outside of the project folder, that output path will now stay put. Previously, it would be incorrectly added to the project folder's path.
- Justified: If you are an Iowa State fan, this update formats your hard disk.
Important: if you want to set output paths outside of your project folder, you'll need to set them one more time after updating to 2.0.3. Also, setting output paths beyond the project folder is not a good idea unless you're sure that project will never be used on a different Mac. Ideally, keep everything in the project folder so that CodeKit can sync the paths across machines.
21 March 2014
Eliminates a few more issues faster than the NCAA Tournament eliminates Duke.
- Fixed: Bower will now work correctly even if Git is not installed on your machine or is misconfigured.
- Changed: Autoprefixer updated to version 1.1. Fixes an issue where initial source maps from Sass/Less files were mishandled by Autoprefixer.
- Improved: The Bower components list will now download much faster and more reliably, thanks to some tweaks to the app and the CDN that powers my website.
- Go Heels.
13 March 2014
Eliminates a few issues that cropped up after the initial launch of 2.0 last week.
- Fixed: possible crash when re-enabling disabled projects
- Fixed: memory leak for Hooks that run bash scripts
- Fixed: tool-tip messages on some buttons were incorrect
- Fixed: editing text values for certain JSHint and JSLint options in the "Defaults For New Projects" area no longer causes a crash AND the values are now saved correctly.
- New: clearing the log will now reset the menu bar icon to black
- Changed: Sass updated to the official 3.3.2 release
- Changed: Compass updated to 1.0.0.alpha.19 (should resolve a few Compass-related issues)
- Unfortunate: 4 beta testers were killed during the production of this update
4 March 2014
Finally, eh? This is a complete re-write of CodeKit. If you're upgrading, MAKE SURE you watch the "Browser Refreshing" screencast; it's totally different now. Don't be the guy that emails me and asks, "Why isn't CodeKit 2 reloading localhost anymore!?"
- Changed: Everything.
- Sped Up: Everything.
- Note: 2.0 is a new app; it will not overwrite 1.x. Do not run both apps at the same time, but you can quit one and switch to the other if needed.
- Note: 2.0 requires Mac OS 10.8 plus. It will not run on 10.7.
- There may be bugs. I have my laptop all day and I'm ready to help. Bear with me; it's a major launch.
- For every bug that shipped, I kill a beta tester.
CodeKit 2.0 includes pre-release versions of Sass and Compass. There are two known issues with this pre-release of Compass:
- If you add any include paths to your config.rb file in a Compass project, CodeKit cannot tell Compass about resources bundled into the app (Bourbon, Susy, etc.) Compass will fix this soon.
- If you have Sass 3.2 and/or Compass 0.12 installed on your system, you may see an error about a "superclass mismatch for class Literal" when performing any Compass actions in CodeKit. To resolve this, run gem uninstall compass and gem uninstall sass on the command line to remove earlier versions of these gems from your system.
1 January 2014
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 crash reporter screen no longer randomly shows up on launch when running Mavericks.
- FIXED: Imported/ignored files are dimmed again on Mavericks. (Ask me how long it took to track down THAT little issue.)
- Less updated to version 1.5. New CSS compressor for Less files is astronomically faster.
- Good stuff around the corner. Hang in there.
23 October 2013
- FIXED: Resolves an issue where Sass, Haml and Slim report errors about non-ASCII characters on Mavericks. (This one wasn't my fault; Apple forgot to specify UTF-8 as the default encoding for the upgraded version of Ruby in 10.9!)
- FIXED: Resolves an issue on Mavericks where GateKeeper falsely reports that the downloaded app bundle is damaged.
20 October 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.
- Looks like I've run out of decimal points. What to do, what to do...
11 September 2013
- Resolves an issue where the Susy Compass plugin may not be detected properly in certain projects.
- Note: I've had reports that PNG optimization sometimes fails for folks still on OS 10.7. I'm looking into it. If this affects you, please email me.
- I almost released an update with no issues.
- This is why they don't let me write software for nuclear reactors anymore.
4 September 2013
- NEW: Bourbon Neat is now built-in. All you need to do is add @import "bourbon"; @import "neat"; to the top of your main stylesheet. CodeKit will do the rest; there is no need to install any files in your project.
- NEW: Susy support for Compass. Compass projects that use Susy will now simply compile correctly right out of the box. You no longer need to switch CodeKit to an external Compass compiler to use Susy. Again, there's nothing to configure. Just add require "susy" to your Compass configuration file and CodeKit will do the rest.
- FIXED: Compass will now regenerate sprites only when needed, which means compiling in Compass projects that use sprites is much faster.
- Less updated to version 1.4.2
- Sass updated to version 3.2.10
- Stylus updated to version 0.36.1
- JSHint updated to version 2.1.10
- JSLint updated to the 26 August 2013 release
- PNGCrush updated to 1.7.67
- ChunkyPNG and OilyPNG (two Compass dependencies) have been updated to attempt to resolve a crash that's occurring on the 10.9 Mavericks Developer Preview. 10.9 ships with Ruby 2.0 as the default environment and these libraries are currently crashing in Ruby 2.0, which brings down CodeKit itself. Be aware of this issue if you plan to update to 10.9! Compass may not work correctly until the developers of these libraries update them for Ruby 2.0 compatibility.
- Other minor bugfixes
- Captain's Log, Supplemental: I'm not sure who coined the term 'twerking', but if we could find that person and not have them on the planet anymore, that would be great.
9 July 2013
- Fixes an issue where Less files in CodeKit Frameworks were not found correctly by Less 1.4.1.
- Does not fix season 4 of Arrested Development.
8 July 2013
- NEW: Less 1.4.1, with a whole slew of new options. Read the documentation over at lesscss.org for details. NOTE: there are some backwards-incompatible syntax changes in Less 1.4, so your code may need revisions after this update!
- Stylus: updated to 0.33.1
- CoffeeScript: updated to 1.6.3
- Uglify.js: updated to 1.3.5
- JSLint: updated to the 2 July 2013 release
- JSHint: updated to version 2.1.4
- Bourbon: updated to version 3.1.8, which brings new awesomeness. See bourbon.io for details. (Seriously, if you write Sass/Scss and haven't tried Bourbon yet, you're doing it wrong.)
- Slim: updated to version 2.0. (NOTE: if you have really old Slim code, you might find that 2.0 throws some errors because it has backwards-incompatible changes. Time to update your code!)
- Node.js: updated to version 0.10.12
- Jade. Ah yes, Jade: the clingy, needy hipster-girlfriend of compilers. Here's the deal: CodeKit is going to continue to support Jade, but for now you should install Jade at the command line and switch CodeKit to use that external Jade compiler (do this in Preferences > Languages > Jade > Advanced Compiler Settings). The bottom line is that Jade has simply become too unwieldy to continue bundling into CodeKit. Jade requires a bunch of third-party libraries, each of which require other third-party libraries, which require yet *other* third-party libraries and so on. It's become a massive web of complexity. Right now, the built-in version of Jade in CodeKit is frozen at 0.30.0 and if you want to use any "filters" in your Jade files, you'll definitely need to install Jade externally. I hope to return to bundling Jade in 2.0, once I have time to sit down and [email protected]# the project.
- On a happier note, I'm going to need some beta testers in a month or so. I'll be making that announcement on Twitter. So if you'd like to see a shiny "2.0" in the About Window before everyone else AND you don't mind if your Mac becomes sentient and destroys your house AND you'll file a bug report instead of a lawsuit when that happens, follow me on Twitter. End shameless plug.
23 May 2013
- Sass --> 3.2.9 (resolves some caching bugs)
- CoffeeScript --> 1.6.2
- Haml --> 4.0.3
- Bourbon --> 3.1.6
- JSLint --> the 16 May 2013 release
- JSHint --> 2.1.2
- An announcement:
- You may have noticed a lack of new features in the last few updates. A few people have even emailed me to ask about CodeKit's future. It's generally a bad idea to pre-announce things, but I really appreciate my users and I want you guys to know that these past few months have been the lull before the storm. In January, I forked CodeKit to begin work on the 2.0 release. In order to incorporate all the features you guys asked for (like source maps, custom build scripts, etc.) and to address many things I discovered only after launching 1.0 (like how teams of developers need to use CodeKit collaboratively), I had to re-design a huge portion of CodeKit's low-level architecture. Along the way, I've used everything I learned in 1.0 to optimize stuff and I've eliminated a bunch of pain points: no more manual project refreshes; CodeKit just keeps up when you add new files. No more locking files on AFP or SAMBA drives (for team environments). And a project that used to take 10-15 seconds to refresh now completes instantaneously --- I had to actually SLOW DOWN the UI so that you could tell something happened. It's ungodly fast. New languages. New workflows. Stuff that people haven't even imagined yet. It's all coming. Rest assured: CodeKit is alive and well. I work on it for hours every day.
- And to answer the questions 8,523 people are about to email me: YES, 2.0 will be a paid update. YES, all 1.0 users will get a big discount. YES, if you buy 1.0 just before I release 2.0, you'll get a free update to 2.0. NO, I don't have a release date yet. All I can say is that I'm over halfway done and can't wait to get 2.0 into your hands. And, most importantly... YES, Panic is going to be jealous.
7 March 2013
- There is an issue in JSHint that may cause a crash when JSHint is run on certain files. This update adds some exception-handling to detect and prevent these crashes.
- You can read the details about this issue and track progress here: JSHint GitHub Page
- As soon as the issue is resolved, CodeKit will be updated. Until then, if JSHint fails on one of your files, use JSLint instead.
- Well, aren't you clever?
5 March 2013
- CHANGED: variables in .kit files are now like Apple's stock price: truly variable. You can overwrite their values. Use wisely!
- Sass updated to 3.2.6
- Stylus updated to 0.32.1
- Bourbon updated to 3.1.1
- CoffeeScript updated to 1.6.1
- (Yes, source maps for CoffeeScript are coming, but they did not make this release because there is a lot of work needed to support edge cases like Coffee files in CodeKit Frameworks.)
- Haml updated to 4.0.0
- Jade updated to 0.28.2
- JSHint updated to 1.0.0
- JSLint updated to 18 February 2013 edition
- Node.js updated to 0.8.21
11 January 2013
- Markdown syntax is now fully supported in Haml files
- Less.js updated to version 1.3.3. (If you use Less, install this update immediately; tons of fixes.)
- Sass updated to version 3.2.5.
- Jade updated to version 0.28.0.
- Slim updated to version 1.3.6
- Stylus updated to version 0.32.0
- Node updated to version 0.8.17
- I would like to take this opportunity to unveil the very first screenshot of CodeKit 2.0, featuring an all-new UI designed by Guy Meyer:
- See, Guy? This is what happens when you don't send me a Christmas card.
- Patched to 1.5.1 to resolve an issue where Less files would not compile if set to compress with YUI.
20 December 2012
- CRITICAL FIX: resolves an issue introduced in the previous update that caused crashes while linking imported Sass and Stylus files.
- The people responsible for the previous update have been knee-capped, Tonya Harding style.
18 December 2012
- NEW: The Kit Language. Kit adds @imports and variables to HTML. Read the documentation and you'll have mastered it in five minutes. It's that easy.
- The algorithms that detect @import statements have been completely rewritten. They are now 13x faster AND they respect comments in every language. If you comment-out an @import statement, CodeKit will not link those files together.
- You can now use the @import url(someFile.less); syntax if you like; CodeKit will link these files correctly.
- Drastically cut the amount of disk I/O involved in linking imported files. Folks still on regular hard disks (as opposed to SSDs) should notice a nice speed bump
- If you delete an @import statement in a file, CodeKit will now unignore the formerly-imported file automatically.
- Compass projects that use sprites should now compile much, much faster.
- CodeKit is now more efficient at figuring out which files create other files. This makes adding/refreshing very large projects several seconds faster.
- Sass --> updated to 3.2.3
- Stylus --> updated to 0.31.0
- Node --> updated to 0.8.16
- Jade --> updated to 0.27.7
- Bourbon --> updated to 3.0.1
- Slim --> updated to 1.3.4
- JSLint --> updated to 17 December 2012 release
- For those of you keeping track at home, @lorenb and I are currently tied 2-2 in our Letterpress battle.
- Loren won the first game. Convincingly. I then slew him twice in a row before falling to the word "zex" in game number four. The fifth game is currently underway.
- If any of you have a surplus of self-esteem and would like me to relieve you of it, I am "bdkjones" on Game Center and I will take on all comers.
19 November 2012
- NEW: Bourbon is completely supported!
- The ONLY thing you need to do to use Bourbon in CodeKit is place @import "bourbon" at the top of your stylesheet and save. It's not necessary to have Bourbon files in your project; CodeKit will just magically make it all work. (See the help page for more detailed info.)
- FIXED: The cache buster is now much smarter and will handle URLs with query strings and anchor tags correctly. There is also now an option to disable the cache-buster completely.
- If you use Project-level settings and rename a project in the sidebar, that information will be synced across machines.
- The Compass and Bourbon menus now have options to take you straight to the documentation for each tool.
- If you run the app from the Status Bar, you'll find a new option to refresh all projects in the Status Bar menu.
- FIXED: Projects can no longer have empty names in the sidebar.
- NOTE: this update will migrate your serial number to a new format. You will not be able to open older versions of CodeKit. (That was never supported, actually, and will usually result in a crash.)
- Finally, it has come to my attention that one, Loren Brichter, has violated my patent on funny release notes. I submit the following evidence to a candid world:
- You think that just because you worked at Apple and Twitter, invented pull-to-refresh, created the first awesome Twitter client and coded part of iOS that you can just waltz in here and start writing funny release notes? Well, sir, CHALLENGE ACCEPTED. I will beat you like a red-headed step child here and then I will smurf you in your own app. (For those unfamiliar with this term, it's when you beat someone in Letterpress by turning the whole board blue.)
8 November 2012
- Explanation: the JSHint folks changed some key stuff in the latest release but didn't tell anyone, so we got caught off guard. The "indentation" value that you set for the syntax checkers is now used only if the "white" value is enabled in JSHint's settings.
- Quicklook support has been added for Slim files.
- Also, apparently we need to have a little public service announcement. Here's the deal: if you find yourself in a zombie apocalypse and you crawl into a freaking tank, DRIVE THE TANK OUT OF THE ZOMBIE APOCALYPSE. Do NOT get OUT of the tank and make a run for it. Zombies cannot bite your spleen in a TANK. This is not a difficult concept.
- (Yes, I just started watching The Walking Dead.)
6 November 2012
- HOTFIX: The original 1.3 release (build 7833) was updated to 7834 to resolve an issue where Uglify.js options in Project Settings were unresponsive.
- NEW: Compass projects can now use CodeKit Frameworks at the same time. It all just magically works. (Thanks to Chris Eppstein for modifying Compass to make that possible!)
- NEW: The project settings area no longer looks like the unholy love child of Gary Busey and Michael Jackson.
- Improved: Refresh times on large projects have been cut by about 45%.
- NEW: For projects that use project-level settings, you can now apply those settings to all existing files in the project with one click.
- NEW: You can now have CodeKit automatically update the "codekit-config.json" file every time you refresh a project that uses project-level settings.
- Related: When you enable project-level settings for a project, you'll now automatically get a "codekit-config.json" file in the project's root folder AND that configuration file will be updated automatically every time the project refreshes by default.
- NEW: You can now export debug information for Less files.
- Fixed: Chrome will no longer reload minimized windows. (And, lo, there was much rejoicing!)
- Fixed: Animated CSS injections in Chrome will no longer affect other animation rules in your CSS. (There was a bug in the injection routine that left a stray animation rule in place after injection completed.)
- NEW: When CodeKit reloads an entire page, it now cache-busts the browser so that your latest changes ALWAYS appear. (You'll see a query string that does this at the end of the URL.)
- NEW: By popular request, you can now disable the animation on CSS injections. (You know, if you're a heathen.)
- Fixed: Imported files with "url" in their name (e.g. "curl.sass") would previously fail to link correctly. That has been resolved.
- For Less files: support for the @import-once syntax has been added.
- For Haml files: support for the CDATA option has been added.
- Fixed: Attempting to hide obscenely large numbers of files all at once will no longer cause a hang.
- Fixed: An issue where Sass/Scss files in CodeKit Frameworks were not detected correctly if you used the Sass partial syntax.
- Fixed: A crash that could occur in rare circumstances when CodeKit attempted to display certain result messages.
- Awww-snap: Compass icons are now fully retina-fied.
- Shazaam: New icons and artwork by the excellent Guy Meyer.
- You can now specify a fonts directory, choose Sass or Scss syntax and choose no "environment" option when creating a new Compass project.
- Stylus files have a new UI for selecting debug information. Fewer checkboxes.
- Large parts of the app are now Helvetica-ized.
- For projects that use project-level settings, a new icon will appear in the scope bar (above the files list) that provides a quick way to get to the settings drawer.
- CodeKit will no longer cause your Mac to switch from integrated to discrete graphics. Translation: better battery life.
- Less --> updated to 1.3.1
- Sass --> updated to 3.2.2 (Media Mark)
- Slim --> updated to 1.3.3
- Node --> updated to 0.8.14
- JSHint --> updated to Release 12. (Adds the "YUI" environment option.)
- JSLint --> updated to the 18 October 2012 version
- CoffeeScript --> updated to 1.4.0
- Uglify.js --> updated to 1.3.4
- Stylus --> updated to 0.30.1
- Jade --> updated to 0.27.6
- Apple should hire me to write change logs for THEIR updates. $#@!-ing "bug fixes"...
23 August 2012
- CRITICAL: Fixes a crash on 10.8 caused by dragging an ineligible file into the "imports" table of the side inspector view. (Example: attempting to import a file into itself.) Strangely, this issue does not manifest on 10.7.
- Fixes an issue where trailing whitespace was left on the comments that indicate the beginning of a new source file in a concatenated output file.
- I don't always update three times in one week, but when I do, I laugh at people who have to put up with the App Store reviewers.
20 August 2012
- Fixes an issue where the Slim language was not available in the Output Paths section of the Project Settings area. Thanks to @openfire3 for reporting the problem.
- See, what happened here is that I spent too much time creating Retina graphics and not enough time actually testing the update.
- Adama is a cylon.
20 August 2012
- NEW: Slim is now fully supported!
- Jade files with "extends" statements will now link correctly so that when you modify a file that extends another, the correct file recompiles.
- It is now possible to set a custom filename and extension for Jade output files. So, you can do "aFile.jade" --> "awesome.php".
- On OS 10.8, Notification Center is now used in place of Growl. Growl remains for users on 10.7.
- The "show notifications" checkbox in the preferences window now actually does what you think it does.
- There is now a "rename" option available when you right-click a project. Because apparently some people missed the memo that clicking something twice in OS X edits it. I'll make sure you get another copy, mmmkay?
- You can now refresh a single project without refreshing all others. This makes it easier to deal with massive projects. To do it, right-click the project and choose "refresh selected project".
- Several UI glitches that appeared when running on 10.8 are now fixed. Note: The UI is now tweaked for 10.8. If you're still on 10.7, you may notice a few things mis-aligned, etc. That's because I don't have a system running 10.7 to test on at the moment. 10.8 is much better. You should upgrade.
- More retina graphics. We're 90% done with this.
- Sass --> updated to 3.2.1
- Compass --> updated to 0.12.2
- JSLint --> updated to the 11 August 2012 build.
- JSHint --> updated to the 19 August 2012 build. (New "unused" option)
- Node.js --> updated to 0.8.7.
- Stylus --> updated to 0.29.0
- Jade --> updated to 0.27.2
1 August 2012
- Resolved several issues with Mountain Lion compatibility.
- FIXED: @import paths that begin with a period to indicate the current directory will now link correctly in the app.
- Killed an edge-case memory leak.
- The file-watching engine (VDKQueue) is now *even* faster. You'd pretty much need an atomic clock to track it, though.
- The status bar icon is now retina-fied. Mainly because some guy requested it on Twitter. His face will soon be introduced to a Retina Macbook Pro traveling at high velocity.
- Node.js --> updated to 0.8.2 (brings full support for UTF-16)
- Less.js --> still at version 1.3.0, but updated to a newer commit that brings support for keyframe animations in WebKit and ratios in media queries.
- Uglify.js --> updated to 1.3.3
- Stylus --> updated to 0.28.2
- JSLint --> updated to the 27 July 2012 build.
- JSHint --> updated to the 30 July 2012 build. (New "camelcase" and "worker" options)
- Sass --> updated to 3.1.20. (Which is like 3.2, if you squint.)
- Jade --> updated to 0.27.0. (Because TJ hates numbers larger than 1.)
27 June 2012
- FIXED: some users experiencing crashes should find that this release fixes those problems. Hopefully, anyway. I can't get the app to crash on my machine, so trying to fix this issue is tough.
- FIXED: an issue where a rename operation on a project folder would not be detected until the project had been refreshed at least one time after adding it.
- FIXED: a bug where canceling a project-adding operation would prevent you from adding new projects until restarting the app.
- FIXED: the registration window will no longer show part of a serial number for new users.
- FIXED: the trial banner no longer collides with the search box when the app enters fullscreen.
- ADDED: more retina graphics.
- You should probably get used to seeing this update screen; there's a ton of great stuff coming in the next few months.
20 June 2012
- Fixed an issue that prevented folks from switching to an external Compass compiler.
- Fixed an issue with external compilers installed through RVM.
- Added support for OilyPNG, which should speed up Compass compiling for people that use Compass's sprites feature.
18 June 2012
- NEW: By popular demand, full support for standard CSS files!
- NEW: You can now tell CodeKit to use external compilers. (The 87,231 people that emailed me about Sass 3.2 beta support should be happy.) See the Preferences window to do it. Keep in mind that if you switch to an external compiler, you're responsible for making sure it and all its dependencies are installed correctly!
- NEW: Vastly refined look and feel in the main window. Smaller, cleaner icons. Output paths now show only on selected rows. (With animation, of course, because this is not a bloody Windows app.)
- FIXED: The inbred cousin of the crashing bug that was fixed in the last update is now fixed. For real this time. CodeKit should now be *rock* solid.
- CHANGED: The output paths pane in the preferences window has been consolidated into the Languages pane.
- CHANGED: Compass projects will now show local imports in the inspector.
- CHANGED: Compass projects now intelligently set output paths on files based on your settings in the Compass config file within your project.
- ADDED: About 50% of the app's graphics are now Retina-ready. If you email me to ask when the other 50% will be finished, I will literally throw your Macbook Pro With Retina Display at your face.
- FIXED: Actions that require the "drawer view" will no longer fail if you're on the Log tab instead of the Files tab when you invoke them.
- FIXED: Issue where a missing, optimized image file showed a "remove" button over top of the green checkmark.
- CHANGED: Minor tweaks to the UI all over the place.
- Updated components:
- Node.js --> 0.6.19. (Much faster compiling!)
- Sass --> 3.1.19
- Jade --> 0.26.1
- Uglify.js --> 1.3.1
- Stylus --> 0.27.1
- CoffeeScript --> 1.3.3
- Bless.js --> 3.0.0
- JSLint --> 9 May 2012 version
17 May 2012
- FIXED: Issue that produced crashes when running on OS 10.7.4
- FIXED: JSHint should no longer return "bad option" messages when using project settings to specify flags.
- FIXED: A bug that could produce random crashes. (Finally got the bastard!)
- Updated Sass to 3.1.18
- Updated Jade to 0.26.0
- Updated Haml to 3.1.6
- Updated Stylus to 0.27.0
- Updated JSHint to the 10 May 2012 release
- Procrastinated: the last two projects separating me from a master's degree.
25 April 2012
- FIXED: An issue where, for some users, switching panes in the project settings area caused a hang.
- FIXED: Jade no longer minifies HTML output if you select the "indented" output style.
- FIXED: A bug in BDAlias that could produce a crash.
- New graphics by Matt Bainton
- Other info: For the next four weeks or so I'm concentrating on finishing grad school. After that, I will get back to adding new features to CodeKit. What's in store will rock your world.
20 April 2012
- REVERTED: The change in build 6143 that addressed lingering missing files has produced crashes for users of macVim and intelliJ editors. I woke up to 92 emails telling me so this morning. As such, this build removes the change so that these users are up and running again.
- If you're not seeing crashes, you can safely skip this update.
19 April 2012
- Fixed: a few people using Espresso reported that CodeKit failed to notice any changes to files after the first save. This build fixes that issue.
- Sparkle updates are awesome, no?
- And just think... if CodeKit had been on the Mac App Store, you wouldn't have gotten this update for a week. Bryan: 1 Apple: 0
19 April 2012
- GOLD — CodeKit is now on sale!
- New: Sparkle updates
- New: Icons for non-common file types (Sass, Less, Jade, CoffeeScript, Haml and Stylus)
- New: The engine that watches for file changes has been replaced with a new, faster, better version that I wrote myself. Speed increases all around.
- New: Keyboard shortcuts. Cmd+R to refresh. Cmd+1, Cmd+2 to switch tabs.
- Fixed: Deleting a file and then creating a new one with the same name will now automatically clear the "missing" file line in the app if it exists.
- Improved: Exception-handling added to the bridge that communicates between CodeKit and browsers. Problems in this bridge should no longer crash the app.
- Updated Stylus to 0.25.0
- Updated CoffeeScript to 1.3.1
- Updated JSHint and JSLint to the latest releases. JSLint now offers the "stupid" flag. Don't ask me what that means; the documentation on the JSLint site literally says: "Tolerate stupidity."
- Updated Jade to 0.25.0
- Updated Uglify.js to 1.2.6
- Updating to this version will clear your project info from the app, but that's the last time!
- Thanks for your support!
28 March 2012
- What? You want more information? The "bugfixes" line isn't doing it for you?
- Some users have seen crashes resulting from a memory exception. The trouble is: the memory exception appears to be in Apple's private frameworks. I have discussed the issue with Apple engineers and this release includes some behind-the-scenes changes that are an attempt to solve this problem.
- I have a "zero-crashes" policy. When I take CodeKit out of beta, I want it to be absolutely rock solid. Sorry in advance if you're one of the users who's seen the app crash, but rest assured: it'll get fixed.
- Updating to this version will NOT clear your project info from the app.
21 March 2012
- Resolves a crash that may occur if you use the "Remove" command in the projects contextual menu.
- Upgrading to this build will NOT clear your projects from the app if you've already installed Beta 10.
21 March 2012
- Browser refreshes are now limited to one every two seconds. Previously, if you compiled many files at once or saved the file you're working on more often, CodeKit would repeatedly instruct browsers to reload many times in one second, which produced hangs in Chrome. This should resolve that.
- External stylesheets are no longer reloaded. If you have a stylesheet in your page's HEAD tag that is NOT local to the project (such as a TypeKit stylesheet hosted on fonts.com), CodeKit will no longer reload that stylesheet. Again, this should solve some hangs.
- NEW: This build includes a crash reporter that you can use to notify me about any crashes.
- NOTE 1: The new browser refreshing time limit means that if you select a bunch of files and compile them all at once (using the compile all button), the browser will refresh after the first file is done compiling. The remaining files may not be done compiling at that point, which means the browser refresh won't capture those changes. I am working on a fix for this now that browser refreshing has a limit. In the meantime, you should avoid compiling multiple files at once AND you should avoid compiling a single file more than once every two seconds.
- NOTE B: If you have scripts that are injecting elements into your page's HEAD element, be aware that this may conflict with the script that CodeKit uses to inject new CSS. If you experience issues, please try commenting-out the script that is injecting things.
- NOTE 87 (for those of you keeping track at home): I'm working hard to resolve the issues folks are seeing with browser refreshes. If you still have problems after this update, please send me an email: bryan at incident 57 dot com. We'll get it working for everyone except duke fans, I promise.
- AWESOME NEWS: Upgrading to this build will NOT clear your projects from the app if you've already installed Beta 10.
19 March 2012
- NEW: Project Settings. It's now dead simple to keep projects synced across multiple machines. It's also now possible to set different default settings for individual projects. See the help page for a full walkthrough BEFORE you use this feature. It's magical and awesome, but you need to understand what the magic is doing for you before you rely on it!
- NEW: You can now "turn off" projects by unchecking them in the list. This stops CodeKit from watching everything in a project. (Use it before doing massive Git or Svn actions.)
- NEW: You can now specify custom global variables for JSHint and JSLint and set them as read-only or read-write.
- CHANGED: Browser reloading is now *massively* more efficient. It also now works with file:// urls and supports Google Chrome Canary. Plus, reloading now happens off the main thread, so CodeKit will never hang or slow down while reloads process. AppleScript has been removed from the equation as well. (You read that right: not only am I injecting changes in browsers WITHOUT AppleScript OR a plugin OR requiring you to add a script to your pages... I'm doing it off the main thread.)
- NEW: You can now set custom filenames and extensions for output file paths. You can even do this on multiple files at once by using a wildcard character. Select the files, right-click and choose "Set Output path".
- NEW: You can now decide what file extensions CodeKit treats as generic webpages. This allows you to have the app watch pages with weird extensions (e.g. CakePHP's *.ctp files) and reload browsers when they change. See the preferences window.
- NEW: You can now set the indentation level for Uglify.js (this only applies if you enable the "beautify" flag on Uglify).
- I've optimized many, many lines of code. The results are a 64.8% decrease in the time it takes to add or refresh a project. This is especially helpful for massive projects.
- Less updated to 1.3.0 --- brings support for "strict" imports
- Compass updated to 0.12.1
- Stylus updated to 0.24.0
- JSLint & JSHint updated
- Eliminated jerkiness in several animations and resolved an issue where the scope selection bar did not draw correctly when the app first starts. Everything should be buttery-smooth now.
- FIXED: crash when attempting to optimize a malformed image file
- CHANGED: the log is now limited to 50 entries in order to keep the app's memory footprint lower. Old entries are removed automatically.
- CHANGED: right-clicking in the projects list is much improved.
- CHANGED: choosing "Use Compass on this project" now gives you the option to install Compass if it's not already added to the project.
- CodeKit is now signed with my Apple Developer ID, making it GateKeeper-compliant on OS 10.8 Mountain Lion.
- This is the final Beta of CodeKit. The app is going gold after a few more tweaks and optimizations.
- IF YOU ENCOUNTER ANY CRASHES, please email the log from ~/Logs/CrashReporter to bryan at incident 57 dot com. Please also include info about how you were using the app when it died.
- Hotfix: Patched to 5943 to resolve an issue where drag-and-dropped import links for JS and COFFEE files were not recreated correctly when adding a project with a configuration file. ONE day I will release an update that doesn't immediately reveal a bug.
17 February 2012
- NEW: "live" browser refreshing. Whenever CodeKit changes a CSS file, your browser will now refresh without reloading the entire page. My thanks to live.js for making that possible. There are no browser extensions to install and no scripts to add to your pages. Note: this feature may not work on really complex sites just yet. Also, CodeKit can't reload file:// urls, so use MAMP to preview your sites!
- NEW: Jade is fully supported. It all just works, including filters for Less, Stylus, Markdown, etc.
- NEW: Completely overhauled the automatic output path settings. You can now specify default output paths for each applicable language. You can also now set output paths by replacing all instances of one path component (e.g. "less") with another ("css").
- NEW: System-wide Quick Look support is now included for Haml, Less, Sass, Scss, Stylus, CoffeeScript and Jade files. No more useless icons when you use Quick Look!
- NEW: Auto-update checking! I *highly* recommend that you leave it enabled, as CodeKit will see frequent updates.
- NEW: Growl has been updated to 1.3. You will now see notifications even if you don't have Growl installed. These can be turned off in the preferences, but they are pretty cool.
- FIXED: A bug that prevented certain import statements from being recognized correctly in SASS and STYLUS files.
- FIXED: A bug that could, in rare cases, cause a crash during the refresh sequence.
- CHANGED: If you have a file with @import or @codekit-prepend statements and you add a new one in the middle, it will now show up in the correct spot in CodeKit. (Previously, it would always be added to the end of the imports list, regardless of where the statement was added.)
- CHANGED: For JS and Coffee files, you can no longer drag to reorder import links that you create with statements in the files. You can only drag to reorder links that you created via drag-drop within CodeKit. (This is so that the order in the table always matches the order of the statements in the file itself.)
- Optimized the import-linking algorithm. When you add a project, CodeKit now links imports about 10-15 times faster.
- Updated Bless.js to version 2.2.1
- Updated Sass to version 3.1.15
- Implemented "Firebug" and "Line Numbers" options for Stylus files. Also fixed a bug that showed SASS output styles for Stylus files. Whoops.
- Optimized drawing code to eliminate subtle UI-jerkiness introduced in Beta 7.
- Updated the import linking routines to respect the Stylus convention regarding "index.styl" files.
- Note: If you previously set custom default output paths, those settings will be discarded in this update. You'll want to set them again before adding new projects to the app.
- Prayer: I changed a metric ton of code in this update. Here's hoping I didn't seriously screw anything up.
- Hotfix: Updated to 5380. Resolves an issue where Less framework files did not appear in the imported files tableView. Also modifies live reloading to apply to CSS changes only. Changes to scripts now reload the whole page. Finally, adds error-checking to handle null content types in stylesheet tags.
26 January 2012
- If you're thinking, "Wow, checking files is gonna be really slow now," verily I say unto thee: "Nay." It chews through 30,000 lines in about two seconds. It finds 804 errors in jQuery instan-freakin-taneously."
- NEW: When seen in the UI, syntax errors no longer look like they were beaten repeatedly with a DOS 5.1 manual (Translation: less ugly.)
- NEW: the auto-hide and auto-ignore options in the preferences window have been replaced by a "skipped items" option. CodeKit will completely skip all folders, files and extensions (specified like "*.js") when scanning for new items. This means they won't count against the 10,000 file limit for those of you with Facebook-sized projects.
- NEW: You can now specify the default indentation level to use for JSHint and JSLint.
- NEW: Compass file inspector introduced so you can now un-ignore Compass files. Huzzah.
- CHANGED: The result log has been tightened up and visually improved for all messages. Syntax errors now present with a contrasting color scheme so it's easy to scroll past them to find regular log messages.
- Fixed: CodeKit now respects the SASS convention of optional underscores on import declarations. If you write @import "base", the app will first look for "base.sass" and "base.scss" in the specified location. If it does not find one, it will look for "_base.sass" and "_base.scss". If neither of those files exist, it will then check any Framework folders.
- Fixed: Clicking the X in the search bar will no longer launch the app into full screen mode.
- Fixed: Two possible memory leaks related to Applescript support
- Added: Growl notifications for Compass actions
- Updated Less.js components to version 1.2.1+. Fixes several bugs, including an issue where error messages may display as "cannot call method 'charAt' of undefined".
- Updated Uglify.js to version 1.2.5
- Hotfix: Updated to 5157 to resolve crash on image optimization. Whoops.
- Hotfix: Updated to 5158 to resolve the same image crash on JPEG optimization. The last hotfix only fixed PNG optimization. The people responsible for the last hotfix have been shot.
- Added: More cowbell.
12 January 2012
- NEW: Compass is now fully integrated. It just works, and it's awesome. See the help page for full documentation on using Compass with CodeKit.
- Updated LESS to 1.2.0
- Updated Stylus to 0.22.4
- Updated Uglify.js to 1.2.4
- Updated JSHint
- Updated JSLint
- NEW: The colored buttons now have shadows. And if you're thinking, "Huh, that's a weird thing to include in release notes," I offer this retort: I spent 9 freakin' hours trying ALL KINDS of button effects on these things, so it goes in the release notes.
- Fixed: When you unhide files, if they were previously not-ignored, they will be so again.
- Hotfix: Patched to 4742 (from 4739) to resolve a gem issue in a Compass dependency.
23 December 2011
- NEW: you can now customize how CodeKit determines which tabs to auto-reload by providing specific strings to search for in each tab's URL. See the preferences window.
- NEW: Output from Less files can now be compressed with YUI for maximum size reduction. Simply change the output style.
- NEW: if you rename a file from X.less to X.sass (or any other combination of formats), CodeKit will now change the file's type appropriately and use your default settings for the new file.
- Less.js components updated to 1.1.6. Brings full support for @media queries & other bug fixes.
- Updated SASS components to 3.1.12
- Updated HAML components to 3.1.4
- Updated CoffeeScript components to 1.2.0
- Updated Uglify.js components to 1.2.2. (Adds support for the new --lift-vars functionality.)
- Fixed: Comments added between sequential CoffeeScript files in an import chain will no longer stop that chain from compiling in certain circumstances.
- Fixed: Text in the log window is no longer cut off for long error messages.
- Changed: New icon for "page" files.
- Fixed: When running the app from the menubar instead of the dock, an "exit fullscreen" button now appears in the top right corner when you enter fullscreen mode. Previously, the only way out was to quit the app!
- Fixed: When the app first started, it was possible to drag the left-hand side to reveal a grey area where the inspector usually sits. This is no longer possible.
- Note: I'm still testing Compass under CodeKit, so I haven't turned on that functionality yet. It'll be in the next build. In the meantime, this build brings a ton of fixes that I didn't want to hold back while testing Compass.
20 December 2011
- New interim build to extend beta expiration until 20 January 2012.
- Testing latest changes & additions; should have a new build with those out in a few days.
20 November 2011
- Haml is now fully supported.
- New, square icons. Because I had to create a Haml one anyway and I didn't like the rounded corners.
- Streamlined the files table. If a file has an associated output (target) file, it won't show the output path anymore.
- Retooled the Languages tab of the preferences window because, well, there were too many preferences.
- If you select a single image, you'll find the dimensions in the inspector. Who says I don't do feature requests!?
- CoffeeScript components have been updated. Resolves several bugs.
- Fix: CoffeeScript files will no longer attempt to compile as a folder instead of a file.
- Fix: No more visual glitches involving filenames when dragging to create import links.
- WARNING: This build will clear all previous data from older builds. There are some low-level changes that necessitate this. Fortunately, it'll only happen during the beta. Once CodeKit goes final, you'll always be able to upgrade without clearing the app's data.
17 November 2011
- Updated the Less.js engine to 1.1.5. This resolves many bugs, including one where CSS Keyframe animations would fail using the % syntax.
- CodeKit will now automatically refresh WebKit Nightlies as well as the production version of Safari.
- Text encoding for @import linking has been changed to UTF-8 from ASCII. All your files should be UTF-8 encoded!
- Pressing command+a while something is selected in the files table will now select all rows. Great for selecting all images!
- Text in the overlay badge (when you drag something onto the window) is now centered.
- Fixed two edge-case scenarios where CodeKit might crash while attempting to log an error.
11 November 2011
- You can now choose to auto-reload either the active tab/window in each browser OR all tabs/windows where the URL contains the text "localhost". The latter setting is now the default.
- Added JPEG optimization support using the jpegoptim library.
- Updated JSHint and JSLint to the very latest versions.
- Fix: the inspector view will now immediately reload after you optimize an image to show the results.
- Fix: you can no longer select files in the "choose output folder" dialog.
- Refined how CodeKit looks at file-deleted notifications in an attempt to support Git branch switching gracefully. CodeKit should no longer crash when you switch branches. If it does, please contact me: bryan at incident 57 dot com. Note: if you switch to a branch with new/different files, you will need to click the refresh button in CodeKit in order to add those files to the app.
- Tweaked the about window design.
5 November 2011
- This is the first public beta release of CodeKit.
- This version expires on 20 December 2011.
- My thanks to all the people who helped test CodeKit back when it was capable of becoming sentient and eating your grandmother. (An especially big thanks to Paul Young and Martin Koistinen!)