Trying out <Zipline> on a new project following the ReadMe, but facing the following issue when runn...

# squarelibraries

[Jishin Dev [JD]]

Trying out Zipline on a new project following the ReadMe, but facing the following issue when running ./gradlew -p lib serveDevelopmentZipline --info --continuous.
Do I have to run any tasks before this one in order to have lib/build/compileSync generated?

A problem was found with the configuration of task ':lib:compileDevelopmentExecutableKotlinJsZipline' (type 'ZiplineCompileTask').
  - Type 'app.cash.zipline.gradle.ZiplineCompileTask' property 'inputDir' specifies directory '/Users/.../lib/build/compileSync/js/main/developmentExecutable/kotlin' which doesn't exist.
    
    Reason: An input file was expected to be present but it doesn't exist.
    
    Possible solutions:
      1. Make sure the directory exists before the task is called.
      2. Make sure that the task which produces the directory is declared as an input.
    
    For more information, please refer to <https://docs.gradle.org/8.2.1/userguide/validation_problems.html#input_file_does_not_exist> in the Gradle documentation.

Please ask if any other info about project setup/versions etc would be required to understand whats going on.

[Andrew Alexander]

I think you might need to run a ./gradlew build to get the directory populated first

[Andrew Alexander]

Otherwise the README might be out of date

[Jishin Dev [JD]]

Running ./gradlew build didn't fix it either. Don't see the /build/compileSync folder being generated. I'm also on the k2 compiler. would it have anything to do with that? Not seeing any errors post the build tho.

[Jishin Dev [JD]]

zipline version - 1.1.0
jdk - 18
kotlin - 1.9.0 with K2 enabled

[Jishin Dev [JD]]

downgraded to 1.8.21, no K2, issue still persists.

[jessewilson]

What’s the javascript {} block in your build.gradle file look like?

[jessewilson]

Ideally something like this:
https://github.com/cashapp/zipline/blob/trunk/samples/world-clock/presenters/build.gradle.kts#L19

[Jishin Dev [JD]]

Almost, this is what I have -

js(IR) {
        browser()
        binaries.executable()
    }

[Jishin Dev [JD]]

Using legacy compiler (without IR or with LEGACY) breaks the build.

[Jishin Dev [JD]]

Anything else you'd like for me to try folks?

[jessewilson]

Hmmm … can you list the lib/build directory and paste that?

[jessewilson]

Zipline attempts to build from where the compiled JS lands and it’s not finding it

[jessewilson]

I wonder why

[Jishin Dev [JD]]

this is all I get after ./gradlew -p lib build

[jessewilson]

Hmmmmm

[jessewilson]

Try lib:compileDevelopmentExecutable ?

[Jishin Dev [JD]]

$ ./gradlew lib:compileDevelopmentExecutable

FAILURE: Build failed with an exception.

* What went wrong:
Cannot locate tasks that match 'lib:compileDevelopmentExecutable' as task 'compileDevelopmentExecutable' is ambiguous in project ':lib'. Candidates are: 'compileDevelopmentExecutableKotlinJs', 'compileDevelopmentExecutableKotlinJsZipline', 'compileTestDevelopmentExecutableKotlinJs'.

[Jishin Dev [JD]]

$ ./gradlew lib:compileDevelopmentExecutableKotlinJsZipline produces the original error.

[Jishin Dev [JD]]

$ ./gradlew lib:compileDevelopmentExecutableKotlinJs passes, but no changes to lib/build dir contents.

[jessewilson]

Iiiinteresting

[Jishin Dev [JD]]

Any other ideas @jessewilson?

[jessewilson]

I’d like to figure out what’s different between your project and ours. Kotlin version? Gradle properties related to JS builds? I’m surprised building the executable doesn’t produce a file

[Jishin Dev [JD]]

I'm sure its something silly thats breaking. 😅

Tried with kotlin 1.8.22 , same as whats used by the sample, issue persists. attaching ss of gradle properties and build files.

Also, If its okay and if it'll help, I can zip and dm the project since its only a skeleton for now and no actual code. lmk.

[jessewilson]

Yes please!