Using .pug instead of .jade results in a write permission error about codekit HOT 10 CLOSED

Sigh. I know what's up. The engine in CodeKit 3 is still the old Jade compiler. It doesn't know what the hell a *.pug file is. I forgot to switch the engine to the Pug NPM module. Will resolve in the next beta.

from codekit.

Well...that's super weird. I'll have to test it on my machine. I have zero ideas why the file extension would matter, but technically it's the pug compiler that writes the file.

Sent from my iPhone

On May 18, 2016, at 11:17, Michael Russell [email protected] wrote:

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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

from codekit.

Yeah, that's what I was wondering, if you were using a different compiler for .pug vs .jade.

I'll do some more testing on my end, setup a new project, etc... and see what happens

from codekit.

yeah, appears to be due to the compiler used for .pug, just tried on a fresh project. compiled successfully, write permission error at end.

from codekit.

Ah. I think I know what this is. Does the output FOLDER where the compiled HTML is going to appear already exist? I believe the problem is that the Pug compiler may be too stupid to create the output folder's path if it doesn't already exist.

from codekit.

Or the opposite: does the output FILE (index.html) already exist and you're trying to overwrite it? If so, Pug may not be overwriting the file correctly.

That "permissions" warning is a generic "I have no fucking clue why this failed, it's probably permissions" message that I spit out whenever the language compiler tells me that it compiled successfully but couldn't write to disk.

from codekit.

In my testings I've tried:

• produce .html beside .pug file
• produce .html in build/ which was already created

both failed but .jade was successful

Also, found that if the .html already exists, triggering a .pug compile will delete that file.

Have you been able to reproduce?

from codekit.

Can you give me the contents of the pug file you're compiling? I don't know Pug.

from codekit.

doctype html
head
    script.
        var test = 'test';
body
    h1 Test

from codekit.

Fixed for Beta 2.

from codekit.