Import your CodeKit projects

XenoKit reads CodeKit 3 (config.codekit3) and CodeKit 2 (config.codekit) project files directly. CodeKit doesn’t need to be installed, and XenoKit never opens it.

Import every project at once

1. Open Import All

   On first launch the welcome offers to bring your CodeKit projects across. Later, choose Import Projects from CodeKit… from the project menu.

2. Choose the projects

   XenoKit lists the CodeKit projects on your Mac, from CodeKit’s own list and Spotlight, with the ones CodeKit has open already chosen.

3. Let it import

   XenoKit installs the tools the projects need once, pins them for each project, and compares each project’s output with CodeKit’s. Every project that comes out the same is imported and starts watching.

4. Review the rest

   Projects that need a decision, such as files that differ or hooks to choose, are shown one at a time to import or skip. A skipped project stays in XenoKit to set up later.

Import one project

Add the project’s folder to XenoKit. A folder with a CodeKit project file opens Import from CodeKit: one page of plain-language cards for styles, scripts, CodeKit’s copies and hooks, the tools and settings kept, and anything that works differently. The check against CodeKit’s outputs runs by itself once the tools are installed.

From Terminal:

$ xenokit import --dry-run  # the report; nothing is written
$ xenokit import --suggested --compare  # compile into a temporary folder and compare with CodeKit
$ xenokit import --dir scss --dir js  # write .xenokit.yml for two folders and add the project

What comes across

• Each folder CodeKit compiles, with its output style, source maps, Autoprefixer, minifying and output paths; files that differ get their own settings.
• Files CodeKit ignores, and CodeKit’s skipped folders.
• Copies and shell hooks, as command rules you choose.
• CodeKit’s Dart Sass and Autoprefixer versions, as version pins.
• Browserslist settings.
• Scripts that use @codekit-prepend and @codekit-append: XenoKit joins them byte-for-byte, as CodeKit did, and marks them with a warning until you port them to import statements.

What doesn’t

XenoKit reports anything it can’t bring over, including CSSO, LibSass, PurgeCSS, Bless, Babel, Rollup bundling, AppleScript hooks, build folders, and files it doesn’t compile, such as Less, Stylus, Kit and CoffeeScript.

Import never replaces an existing .xenokit.yml.