bdkjones / codekit Goto Github PK

Quick, short summary:
In a new project, files are not processed on change despite the Output setting. Manually clicking the 'Process' button for the file works, but new changes to the file do not correctly output a process file.

Expected results:
A file is saved, a processed version is output.

Actual results:
A 'Refresh Complete' lower banner notification appears, but no processed file is output unless the 'Process' button is manually clicked.

Project added, output settings shown:

Default settings:

File is saved, 'Refresh complete' banner appears.

No output files created. Empty log.

'Process' button clicked, file is processed.

Exact steps to reproduce:

1. Create a new folder
2. Add folder to CodeKit
3. Make a new file ( main.js )
4. Verify CodeKit's default output settings are set to process the file
5. Make changes to file and saved.

A link to download a simplified project or file that shows the issue:
File Processing Test.zip

Your configuration (any details about your system that you think might be relevant)
The project is brand new for CodeKit 3 (never been added to CodeKit 2), but my default output settings look like they've been migrated over from CodeKit 2.

Quick, short summary

Files with over 200 working files take forever to refresh, and I can't isolate the folders because of the size of the project. We have stylesheets/js/php that get served on specific devices on a very large enterprise application so I can't make codekit just watch 1 or 2 specific folders.

Expected results

Quick refresh upon adding a new file, for example, a JS file.

Actual results

Takes 1-2 minutes sometimes. Once it took 3 minutes.

Your configuration (any details about your system that you think might be relevant)

Macbook Pro 2014 15" retina 2.7GHz i7
10.11.5

Notes

I've been using gulp/grunt, and it appears that gulp/grunt config files are still the best method for large applications.

Quick, short summary:
First of all, I have to say that hooks were awesome in CK2 and are even more useful in CK3. Being able to process any file type (an thus trigger a hook) helps a lot. For example, I have a transpiler I made to make useful JSON files out of XML schema files I have no control over. I used to have to change the .xml extensions and process it as another type of file in CK2. It's nice to work with the file natively now. Two minor suggested enhancements for how Hooks work:

1. Pipe bash/terminal feedback to a codekit screen. Right now, if you have a bug in a hook script, you have no feedback what is causing an error. I am not a bash expert, or even a good speller, so I make a lot of mistakes. It would be nice to have the option to see what you might otherwise see in a terminal window after executing commands so it is easier to debug and see status. I understand that hooks can't be interactive, but a little feedback would help.

2. Trigger hooks on specific files in the files tab. Currently, you determine when a hook is triggered using the series of pull down options (name/path->matches/contains/end in/etc) in the settings -> hooks tab. If you want to process a specific file or set of files, you have to make sure you use a set of descriptors that match the file(s) you want and not others you don't want to trigger the hook. This requires naming conventions and coordination between the rules and files. It can also become brittle when names and paths change. It would be nice to have another option in the files tab "when this file changes or builds, activate hook". This will allow you to easily apply the hook to a file, change the filename, process other files, and not have to constantly coordinate descriptors.

Good stuff in CK3!!

Expected results:
Ability to see bash/terminal results of running hooks. Ability to apply hooks to individual files.

Actual results:
No terminal feedback. Use a series of file/path descriptors to trigger hooks.

Exact steps to reproduce:

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)
Codekit 3.0 build 23903

I ask because when I want to copy an html/php/etc file to the dist folder I have to press the refresh button or save a js/sass/svg/etc for it to copy it.

Quick, short summary:
The (x) button over the project icon to remove project is not available in the Project Sidebar.

Expected results:
The (x) button would appear over the project icon in the sidebar when hovered, like in the Project Dropdown.

Actual results:
No (x) button appears.

Quick, short summary:
The project title has jumped down away from its icon. I suspect a divorce.

Expected results:
The project title should stay with the icon through thick and thin just as they promised when they took their vows.

Actual results:
The project title has abandoned the icon, the icon doesn't know why :(

Exact steps to reproduce:
No idea how to reproduce, it just happened, they must have had an argument

A link to download a simplified project or file that shows the issue:
Quitting fixes the issue and it seems that the title and icon are having regular counselling sessions

Your configuration (any details about your system that you think might be relevant)
iMac mid 2010 27", OSX 10.11.5, CK3B1

Quick, short summary:
Currently you can create a main.ts file and import other .ts or .js files and if selecting system or amd module formats for outputs tsc will bundle all the imports into one outFile. This is great for having a ready to use file with all your code.

However, if say main.ts imports maths.ts and we update maths.ts we don't get a new main.ts generated with the new code from maths.ts in place, we have to go to main.ts and re-save it to get the updated code from maths.ts into the outFile of main.ts.

This behavior would be very much like @import in SCSS files.

Docs on how module resolution works https://www.typescriptlang.org/docs/handbook/module-resolution.html

Expected results:
If I edit an imported file the file that imports it gets re-processed with the new code.

Actual results:
I have to save the file that imports the updated module to get the new code.

Exact steps to reproduce:

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)

Quick, short summary:
When I open certain projects from Coda (using CodekitCodaPlugin 1.0), a very large project called 'test' is opened with over 70,000 files within my base user account. It takes several minutes for this file to open. If I delete the project from Codekit, it will re-appear when I open the project. Because it is so large, it takes several minutes to open and locks up Codekit unitil it opens.

Expected results:
If I delete it, it gets deleted.

Actual results:
It's the cat that keeps coming back, and shows up in Codekit 2 as well. Why won't it die?

Exact steps to reproduce:
Open certain projects in Coda

A link to download a simplified project or file that shows the issue:

Archive.zip
Codekit-test-bug.zip

Your configuration (any details about your system that you think might be relevant)
Codekit 3.0 build 23903, Coda 2.5.16, CodekitCodaPlugin 1.0

Quick, short summary:
Since TypeScript has moved to a super set of JS, it's now a pretty decent JS transpiler.

Expected results:
See TypeScript as an option to transform JS.

Actual results:
Only see Babel as an option to transform JS.

Exact steps to reproduce:

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)

Quick, short summary

CK3 lets me choose/change the output path for Sass files in a Compass project but ignores the setting.
It's granting me the option to change it but then silently decides "you're not in charge sunshine, config.rb is"

Expected results

Deny changing the path and show a dialog box like in CK2:

To change the output path for Sass files in a Compass project, you must edit the "asset paths" in the config.rb file within your project.

Actual results

I can change the output path clicking "Change" next to the file's path.

Exact steps to reproduce

• Create project.
• install Compass
• Change a compilable file's output path

Your configuration (any details about your system that you think might be relevant)

MB Pro (Retina, 13', Mid 2014), OSX 10.11.5, CK3B1

Quick, short summary:
Attempting to rename a group requires clicking on one of the first three characters in the group, otherwise the click is ignored.

Expected results:
Clicking anywhere on the group name is enough to bring up the rename field.

Actual results:
Clicking in the region of on one of the first three characters in a group (shown in red below) will bring up the rename field. However, clicking anywhere else on the name won't do anything.

Exact steps to reproduce:

1. Create a New Group via your favorite method.
2. Click on the word Group of that group name. Nothing happens.
3. Now click on the word New of that group name. You can rename it.

A link to download a simplified project or file that shows the issue:
None needed.

Your configuration (any details about your system that you think might be relevant)
OS X 10.11.5 / CodeKit Beta -- Version 3.0 Build 23903

Quick, short summary:
CodeKit's Menu Bar options are not available when the app is run with Show App Icon In: The Menu Bar only. Currently that's the only way to toggle the Projects Sidebar without the keyboard shortcut.

Expected results:
Ability to show/hide projects sidebar from the Projects Menu.

Actual results:
Menu Bar only

Dock or dock & menubar

Exact steps to reproduce:
Preferences > Show App Icon in "The menu bar only"
Cannot toggle Projects Sidebar without knowing the Keyboard Shortcut

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)
OS X 10.11.4
MBP Retina, 15in, Late 2013

Quick, short summary:
At some point CK thinks a project is missing from disk

Expected results:
For CK to not think a project is missing from disk

Actual results:
CK states project is missing from disk https://www.dropbox.com/s/1mmkusb5awo1u50/Screenshot%202016-05-18%2022.54.02.png?dl=0

However, everything works correctly from what I can tell when saving files, they compile/move/whatever they should do...

Exact steps to reproduce:
Not really sure, this has happened twice...

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)
May not be relevant but I have a SSD.

Quick, short summary:
Small nitpick here, there is no option to view Codekit in full screen mode. I use Mission Control in Mac with my IDE and several defferent browsers and other applications open in full screen. I like to have Codekit next to my IDE so when I save the file and focus shifts to Codekit to show me ESLint report, it doesn't go all the way to desktop. It causes a lot of extra swiping

Expected results:
Have a full screen option

Actual results:
Can only view in large mode, not full-screen

Exact steps to reproduce:
N/A

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)
Codekit 3.0 build 23903, Coda 2.5.16, CodekitCodaPlugin 1.0

Hi Bryan,

While its not a code bug, I have a 27" iMac. I think the wrapping element should give enough space to the text, was this done on purpose?

I think it ruins the user experience.

Looking slick 👍

Quick, short summary:

See full text

Actual results:

Open app

A link to download a simplified project or file that shows the issue:

No project needed.

Your configuration (any details about your system that you think might be relevant)

N/A

Quick, short summary:

When the global path for Sass is ../css it uses it even if the project's settings are different.

I'm using the PHP Laravel framework, so the files are on /resources/assets/css/, and the compiled ones are on /public/css/. My Project's settings set they are on that folder relative to the project's root. While my global says they are relative to the file on ../css.

I changed the global's path to something else and it stopped doing double, but changing it back to ../css makes it compile it again on the global settings instead of the local files.

Expected results:

To compile the file only in the project's settings chosen path.

Actual results:

It makes TWO files on the folder ../css relative to the file, even when the project's settings say otherwise.

It made this two compiled files when my original file is named "style.scss":

../css/style-ck.css
../css/style.css

When it should've only been on /public/css/style.css, and it keeps refreshing those 3 files.

This is also the file extract on the codekit3.config:

"\/resources\/assets\/sass\/style.scss": {
        "createSourceMap": 0,
        "debugStyle": 0,
        "decimalPrecision": 10,
        "fileType": 4,
        "inputAbbreviatedPath": "\/resources\/assets\/sass\/style.scss",
        "outputAbbreviatedPath": "\/public\/css\/style.css",
        "outputAction": 0,
        "outputFlags": 0,
        "outputStyle": 3,
        "shouldRunAutoprefixer": 0,
        "shouldRunBless": 0,
        "useLibsass": 1
        },

Exact steps to reproduce:

1. Change your global Sass settings so the files are compiled on ../css relative to the folder.
2. Change your project's settings so the file is compiled somewhere else.
3. Save your .scss

Quick, short summary:
All these are complaints are on a very high level. But since I am a proud CK3betaboii, I can't miss out on this opportunity to nip-pick :)

The visual design is undoubtedly a huge improvement. But imo the attempt to stay clean went too far; compared to CK2 it feels like this new UI lacks focus? Maybe it just needs some kind of visual roof again ;D – It is visually very "cautious" and feels quickly overlookable TAB-ing through my 129 open windows.

The compile button needs (I skip the imo from now on, okay?) some kind of Call to action look. You may not want it to be too present– but in the current state it just adds up to the general "too flat clean bla" –

I felt so free to suggest some tweaks and minor adjustments in a screenshot.
Maybe you share my thoughts.

But in the end – just my feelings looking at and using the app; don't slaughter me!

Just a thought but I use the osx dark ui 24/7 and it would be nice if the codekit icon had an inverse option so it stands out and makes me say "mmmm taste."

Feel free to lambaste me on this non bug

Quick, short summary

I was trying to use the new .pug extension for .jade files and it compiled successfully but I was hit with a write permissions error. Changing the extension to .jade fixed the write permissions error and index.html was created successfully.

Expected results

saving the index.pug file to create a index.html file

Actual results

index.pug was compiled successfully but CK was unable to write to my file system due to a permissions error. I check the permissions and all is fine, and it's especially interesting that the .jade variant was OK with being written to that folder.

Exact steps to reproduce

• created a simple project with a source/ and build/ work flow
• add a minimal index.pug file with doctype/head/body/h1
• save index.pug

Right now, in my hooks, I usetell application "CodeKit" to display alert "..."to display errors and warnings, should anything go wrong.

But it would be much cooler, if those messages just showed up in the normal log, instead of interrupting my work with dialog boxes. Something like:

tell application "CodeKit"
    -- type: error/warning/success
    -- return value: 0 on success, 1 if no project/framework contained the path you supplied, 2 if a problem occurred
    if ( log error "..." for path "..." ) > 0 then 
        -- display a dialog, instead
        display alert "..."
    end if
end tell

Quick, short summary:

When using PHP Laravel framework, there's a folder called "Storage" that stores the sessions info and compiled php views, etc.

When saving any php file it does't auto refresh the site, and when you manually refresh the sites, it compiles a sessions file (and MD5 filename without extension) and it just adds a dot at the end of the file:

Expected results:

To leave those files alone.

Actual results:

It is compiling them without reason, and the compiling is just adding a dot to end of the filename.

Exact steps to reproduce:

1. Use Laravel PHP framework
2. Save any .php file of your views
3. It won't automatically refresh with the Browser Refreshing
4. Refresh the site manually
5. Wait for the compiled notification, because a session file is modified.

I was wondering the reason behind adding the prefix -dist.js to processed files when using a build/ source/ workflow?

Quick, short summary:
When there are no projects, the New Group option is offered under the CodeKit logo button, but doesn't do anything when selected.

Expected results:
A new group should be made or the choice shouldn't be available.

Actual results:
Selecting the choice "New Group" does nothing with no projects created.

Exact steps to reproduce:

1. With no projects made, click the black CodeKit button.
   2A. Then either press the hamburger menu on the left...
   
   2B. Or press the + sign on the right...
   
2. Select New Group from the menu.

A link to download a simplified project or file that shows the issue:
None needed.

Your configuration (any details about your system that you think might be relevant)
OS X 10.11.5 / CodeKit Beta - Version 3.0 / Build 23903

Currently, the only way I know how to bundle JS files is with the good o'l // @codekit-append/prepend.

This has worked great, but, now that things are venturing into the ES.Next world I was curious if you'd put thought into doing bundles with something like systemjs or amd?

You could have some restrictions in place like the latest typescript compiler where bundling only works when using either of those two module export types.

Or will this be in hook land?

Quick, short summary:
When importing a new project there is no visual cue to show that the import is occuring.

Expected results:
Drag a medium sized project onto the codekit window (Add as a project) and a spinner or loading bar animates while the files are imported.

Actual results:
Screen returns to pre import state and appears static. Package import displays down bottom and what appears to be a loading bar has a static image.

A few seconds later the project loads and refreshes the page.

Exact steps to reproduce:
Drag new project onto (Add as a Project)

I only mention this because my first instinct when it happened was that it had done so really quickly and then I checked the list of imported projects and it wasn't there and I thought it had failed. What had actually occurred was that it was still loading.

1. When you resize the window while on the settings "tab", the content stays the same width, so a blank space appears to the right
2. The content should also resize, or lock the window so you can't resize it on Settings
3. Not resized nor locked
4. Go to Settings (either global or project's) then resize the window to the right

I renamed the App to CodeKit3 so it can go in my app folder without overwriting CK2. Is that not recommended?

Quick, short summary:
When using Coda 2 plugin, opening projects in Coda automatically opens Codekit 2.x unless I have Codekit 3 open prior to opening project in Coda. This can cause logistical shuffle when Codekit 3 crashes or is closed, as Codekit 2 will be opened automatically. You have to close the Coda 2 project, re-open Codekit 3, then re-open the Coda project.

Expected results:
Codekit 3 is liked as default to open when opening Coda projects

Actual results:
Codekit 2 is opened

Exact steps to reproduce:
Open project in Coda without Codekit already open

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)
Codekit 3.0 build 23903, Coda 2.5.16, CodekitCodaPlugin 1.0

Quick, short summary

I was trying to remove the *-dist.js suffix from my JS files when using the new source/ build/ workflow and found that CK added a main-dist-dist.js file to the build/

Expected results

Not see a file called main-dist-dist.js in build/

Actual results

Found a main-dist-dist.js file in build/

Exact steps to reproduce

Start a new project and select "This project uses a build folder", kept the defaults source and build.

Select js file to process and update its output path to not have -dist.js prefix.

A link to download a simplified project or file that shows the issue.

https://github.com/subhaze/ck3_test1

Your configuration (any details about your system that you think might be relevant).

https://www.dropbox.com/s/7virww2m6caccd3/Screenshot%202016-05-18%2010.23.32.png?dl=0

Quick, short summary:
If you rename a project folder, the same project can be added to CodeKit twice, though both are still monitoring the same folder.

Expected results:
The project would not be listed twice.

Actual results:
The project is listed twice

Exact steps to reproduce:

1. Make a folder
2. Add folder to CodeKit
3. Rename folder
4. Add folder to CodeKit
5. Create a file in the folder
6. Refresh both projects to verify that they are monitoring the same folder

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)

Quick, short summary

I doubt anything besides a quick summary is necessary. I enabled ESLint on a JS file and got many "require" errors and I figured it's because I use Node syntax, after enabling the Node environment I saved the file again and this time I just got, "ESLint found 1 issue:" and it would not display what the issue is, after saving a few more times it finally displayed what the issue was.

Expected results

ESLint displaying what the issue was.

Actual results

ESLint saying, "ESLint found 1 issue:" with no log.

Exact steps to reproduce

1. Load the following code with default ESLint settings on:

var test = require('example');

1. Save it
2. Should throw some errors
3. Enable the Node environment
4. Save again
5. Save again to get the actual log to display

Your configuration (any details about your system that you think might be relevant)

I am working in a very large laravel project (1500+) files

Extra notes

This is also an issue with JSHint sometimes not even displaying what the error is on creation of a JS file. It just says "Found X issues:" and the log doesn't work.

Quick, short summary:
Saw the Gene Wilder project icon and figured I could some how replace it with one of my own based on where the ⓧ was located.

Instead it deleted my project from CodeKit 3 (though it could be recovered by re-adding).

Expected results:
Something that's related to deleting the project should:

1. Be more obvious that the project itself is being affected ... like this (red coloring to highlight position, not style):
   
2. As data is being removed, a confirmation dialog ought to appear. Ideally warning that the removal is non-destructive, and the project can be recovered by re-adding, but that it just won't be in the CodeKit project menu anymore.

Actual results:
The project will be removed instantly.

Exact steps to reproduce:

1. Open the project menu.
2. Click on the ⓧ that's on the icon.

A link to download a simplified project or file that shows the issue:
Not necessary to reproduce.

Your configuration (any details about your system that you think might be relevant)
OS X 10.11.5 / CodeKit Beta - Version 3.0 Build 23903

Quick, short summary:

The Skipped Folders field on the General settings only shows 2 lines, but when selecting it to edit it it shows all the other lines.

Expected results:

To show all lines since the beginning.

Actual results:

It only shows 2 lines when the field is not on focus.

Exact steps to reproduce:

Go to Settings > Project Settings > General and click on the the Skipped Folders field.

Quick, short summary:

On CodeKit 2 after an image was optimized it showed a check indicating it was already optimized, now there's no indicator.

When trying to optimize for a second time a JPG image it gives this error:

JPEG Optimizer: Unable to optimize this file. It may be corrupt or damaged. Try re-exporting it from your image editor.

Some other images like this one: http://jaimeeee.com/_public/package-adult.png have a 0 bytes initial size:

Expected results:

To have a checkmark if the image has been optimized already, and show the correct initial size.

Actual results:

There's no indicator if an image is already optimized, if you try to optimize an already optimized JPG, it will throw an error.

Exact steps to reproduce:

1. Select an image
2. Click on the Optimize button

Quick, short summary
The red "lost contact with CodeKit" bar is constantly appearing when viewing the project through the .local domain.

Expected results
You should click this so that it can re-establish the connection to CodeKit and it should correct itself.

Actual results
The page will refresh, but the connection back to CodeKit cannot be made so the red bar persists.

Exact steps to reproduce

• Added project to CodeKit
• Viewed project via .local:5757 domain
• Visited new page and problem occurred

A link to download a simplified project or file that shows the issue.
https://www.dropbox.com/s/l22yvs5z2qpktp1/hector.zip?dl=0 (just theme that is the actual CodeKit project)

Your configuration (any details about your system that you think might be relevant).

• Running OS X 10.11.5
• The CodeKit project is a WordPress theme
• Using MAMP Pro (most current version) as server and doing browser refreshing via the MAMP Pro URL
• Tried restarting CodeKit, MAMP Pro, and also removed and readded the project to CodeKit
• Added a completely new project to CodeKit and have the same issue

Quick, short summary:
Not having "Create source map" check still produces a source map.

Expected results:
To not see a source map generated for js file.

Actual results:
A source map file is generated for js file.

Exact steps to reproduce:
Process a JS file with babel and a source map is produced.

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)

Quick, short summary:
.jsx is not seen as a js file and is ignored (as far as I can tell). I can obviously easily just rename the file to js (and with that, everything works as expected with the appropriate babel presets set). But on larger projects would be painful to rename everything

I have noticed that using a non-retina mac, the text appears distorted and slightly blurry.

You can see the difference between the text on the left and right panel:

I would also note that Foundation Icon Looks way to low res.. Is it a vector icon?

Expected results:

Clear crisp text.

Actual results:

Blurry Text

Exact steps to reproduce:

Create a new Foundation project, desktop folder.

A link to download a simplified project or file that shows the issue:

N/A

Quick, short summary:
Babel outputs messages with a monospace font in mind, and places a ^ indicator to let you know where you failed at life. At the moment, Codekits log is not using monospace, making it hard to catch where the error is actually occuring

Expected results:
Monospace font in log

Actual results:
Non-monospace font in log

Exact steps to reproduce:

• Babel -> Presets -> React, ES2015, Stage-0
• Make a simple error (see screenshot below with semicolon in wrong spot)
• Save
• Read error (see screenshot - note the ^ should be under the ;

Quick, short summary:
Instructional text should never be truncated by the size of its dialog box.

Expected results:
All instructional text should never be truncated by default.

Text should fully read: Sadly, you have no projects.

Actual results:
The text "Sadly, you have no proje..." appears.

Exact steps to reproduce:
Open CodeKit 3 Beta, click the black CodeKit logo button (don't know what this is officially called).

A link to download a simplified project or file that shows the issue:
None needed, see the inline graphic.

Your configuration (any details about your system that you think might be relevant)
OS X 10.11.5 / CodeKit 3.0 - Build 23903

I saw this comment on a closed thread and wanted to add my vote to it and give others the option to chime in as well.

I definitely understand the reason for the smart resizing based on what panel you are viewing, but it is driving the OCD part of me insane to keep having the window resize.

I know you never want to simply "add an option" for everything under the sun cause it will just complicate things in the end, but this is officially my vote to have this disabled, or there be an option to disable, the smart resizing in CodeKit.

Quick, short summary:

ESLint issues are shy.

Expected results:
Show me the money, Jerry.

Actual results:
Issues aren't displayed in the log.

Exact steps to reproduce:

1. Process a JS file with JSHint.
2. Change the file options to use ESLint.
3. Process JS file.

The log is displayed with missing issue list.

A link to download a simplified project or file that shows the issue:
If you really need the file, you can find a copy here. But no making fun of my code. It gets minified for a reason.

Quick, short summary:
JSHint incorrectly displaying the "limit of 1000 errors" message when transpiling with babel react preset.

Expected results:
No warning message when transpiling.

Actual results:
Warning message

Exact steps to reproduce:

• Babel -> Preset -> React (nothing else)
• Simple line of react: var a = <p>hi</p>;
• Save
• Warning is produced

Note The file does transpile correctly

Quick, short summary:
The content body of the list of components scrolls left and right, though appears it shouldn't

Expected results:
For the list of components/creators to only scroll vertically

Actual results:
Scrolls vertically and horizontally

Exact steps to reproduce:

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)
I don't have a cool new retina display

Quick, short summary:
Copied an un-optimized SVG, renamed it, saved it after making a minor change. and CodeKit optimized that file in place overwriting my nicely formatted SVG.

Now that I attempt to replicate, it seems that sometimes copying, renaming or saving an SVG will trigger CodeKit to optimize it in place. The 'When this file changes or builds' setting by default is 'Optimize it', but CodeKit does not seem to obey that when the file is changed.

Expected results:
Only optimizing from source to build folder, or opt-in for optimizing in-place.

Actual results:
SVG optimized in place, overwriting the original.

Exact steps to reproduce:
I cannot replicate this every time, but these seem to be the steps:

1. Copy an SVG
2. Rename or save the SVG
3. Sometimes the new SVG is optimized in-place.

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)

I understand that if you wish to select specific plugins the Presets must not be checked, however, I'm curious if the UX could be reworked to where instead of having to check/uncheck all the specific plugins associated to the preset it could be a select all/none toggle.

Say... I use the System module transform plugin a lot, I've immediately lost the ease of just having "ES2015" checked. So my thought was, just using the preset checkboxes as "select all" check boxes for the specific plugins below, click ES2015 and all the plugins below under ES2015 Transform Plugins get checked, if I ended up checking all those, the have the ES2015 preset above checked.

That way it's one click to select everything/nothing.

Or... maybe have a "select all/none" above each group of plugins (some, like the modules section may not make sense to have this) which would greatly reduce the clicking friction when your workflow puts you in a spot where you'll most likely always need more than the presets.

Thanks for the beta release! Only played with it for a bit now, but loving the UI/UX updates compared to 2!

Quick, short summary:
The hell's this?

Expected results:
To know what the hell's this.

Actual results:
Don't know what the hell's this.

Exact steps to reproduce:
Spend a moment in my shoes and look at it.

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)

Quick, short summary:
Currently you can create a main.ts file and import other .ts or .js files and if selecting system or amd module formats for outputs tsc will bundle all the imports into one outFile. This is great for having a ready to use file with all your code.

However, if say main.ts imports maths.ts and we update maths.ts we don't get a new main.ts generated with the new code from maths.ts in place, we have to go to main.ts and re-save it to get the updated code from maths.ts into the outFile of main.ts.

This behavior would be very much like @import in SCSS files.

Docs on how module resolution works https://www.typescriptlang.org/docs/handbook/module-resolution.html

Expected results:
If I edit an imported file the file that imports it gets re-processed with the new code.

Actual results:
I have to save the file that imports the updated module to get the new code.

Exact steps to reproduce:

A link to download a simplified project or file that shows the issue:

Your configuration (any details about your system that you think might be relevant)

Quick, short summary:
CodeKit 3 sports a beautiful clean interface with smooth friendly icons. @guymeyer and @bdkjones did such a beautiful job that it inspires me to point out some really small issues with 4 icons.

Of course, this is all quite subjective and you can obviously ignore it. Still, this is what I experience when I use the application, and it may be helpful if I mention it. :)

Expected results:
All icons are excellent.

Actual results:
There are 4 icons that could be better:

1. Currently the "Logs" icon looks like a terminal icon with a prompt. Misleading as there isn't any prompt inside the logs, I cannot type commands there; it's rather a list of log lines. Something with horizontal lines would be more appropriate. (I also find strange that the box-line on the left-hand side is missing: it looks broken to me as if the displaying of the icon got distorted.)
2. The "cog" icon for settings looks beautiful on a retina screen, however on a non-retina screen it gets square-y as in a diamond shape (see screenshot below).
3. The (green) dot for "server status" is a good idea but it is so similar to the standard OS X green zoom button not far away from it that it can get confusing. It would be great to change it to some other shape. Maybe green checkmark / red X or something like this?
4. The preview icon is quite different from the other icons. It would be better if it would be a square and not a rectangular. Also, the arrow inside the window doesn't add much to the value (especially on a non-retina display where the arrow is blurry). All in all, I think a simple ► button (Play) would much better express what this button is about and could better rhyme with the "server status" icon next to it.

Quick, short summary:
[edge case] If quitting directly from a settings panel, doesn't save the updated settings

Expected results:
For it to save the settings

Actual results:
Does not save settings

Exact steps to reproduce:

• Go to settings
• Change settings
• Cmd + Q
• Open codekit
• Setting changes gone

A link to download a simplified project or file that shows the issue:

quit-no-savey.mov.zip

Your configuration (any details about your system that you think might be relevant)
NA