I tried with both Safari an Chrome .. both seem to...

# javascript

[Jonathan Smith]

I tried with both Safari an Chrome .. both seem to have the same issue.

[Jonathan Smith]

When I run browserDevelopmentRun I also get a bunch of warnings that might provide some hint on what is going on:

> Task :kotlinNpmInstall
warning workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > webpack-dev-server > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > webpack-dev-server > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > webpack-dev-server > http-proxy-middleware > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see <https://github.com/lydell/urix#deprecated>
warning workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > webpack-dev-server > http-proxy-middleware > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: <https://github.com/lydell/resolve-url#deprecated>
warning "workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > kotlin-wrappers-kotlin-styled-jsIr > styled-components@5.3.0" has unmet peer dependency "react@>= 16.8.0".
warning "workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > kotlin-wrappers-kotlin-styled-jsIr > styled-components@5.3.0" has unmet peer dependency "react-dom@>= 16.8.0".
warning "workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > kotlin-wrappers-kotlin-styled-jsIr > styled-components@5.3.0" has unmet peer dependency "react-is@>= 16.8.0".
warning "workspace-aggregator-28a4e29d-6b6e-4a4c-8723-90b1cf68b356 > likely-tag-editor > kotlin-wrappers-kotlin-react-dom-jsIr > react-dom@17.0.2" has unmet peer dependency "react@17.0.2".

[Jonathan Smith]

I also tried both IR and Legacy compilers . . no luck

[Jonathan Smith]

SO.. I created a project from the template and did not change any of the settings or files…

[Jonathan Smith]

So apparently it does not work even without any of my code..

[Jonathan Smith]

So eventually I created an issue .. not sure what else I can do.
https://youtrack.jetbrains.com/issue/KT-46608

To be sure other than the debugging problem things were going very well. (I am porting over some pretty involved UI code from a JS React project.) I had hopes that I could use Kotlin and avoid spending 6 months using a back-end language and six months using JavaScript.

But if the debugger does not work, it could slow down me tracking down an issue when it seems to be fixed quickly. Thanks much for any advice!

[Sean Keane]

@Jonathan Smith FYI - Seems that you will begin to see some sort of source map on 1.5.20 according to this ticket.

https://youtrack.jetbrains.com/issue/KT-46551

[Jonathan Smith]

I did some more experiments early this morning with my debugging woes that turned up some interesting clues:

1/ I tried the same procedure, creating a fresh Kotlin/JS React project, on another computer. I had not yet updated the Kotlin plugin on that machine. In Chrome it worked fine .. I was able to see the source files, set breakpoints etc. (Safari did not work, but I was not really expecting it to.)

2/ Then I updated the Kotlin plugin, created a new project, and that failed again.

[Jonathan Smith]

So 3/ I opened the project I had created with the old plug-in and I was still able to see the source, set breakpoints, etc. It seems the problem may be with a template associated with the new version of the plug-in?

[Jonathan Smith]

@Sean Keane Thanks! However, I am not using the IR compiler at present for any of these experiments.

[Jonathan Smith]

@Sean Keane Good news though! I do hope to have a sourcemap in the IR compiler soon 🙂

[Jonathan Smith]

I wonder if there is a way to back out a new version of the plugin .. looking in to that!

[Sean Keane]

(Safari did not work, but I was not really expecting it to.)

😂

It should work if you're not using the IR comp...

[Jonathan Smith]

Hehe well Safari. I won’t worry about it. All of my users use Chrome 🙂

[Sean Keane]

Thats some pretty heavyweight assumptions you got going there...

I like your style. 🎉

[Jonathan Smith]

I am blessed. My audience is a small group of statisticians and political scientists. Not many web developers have such a small user population (about 25) and guaranteed to all use the latest version of a single browser. On the other hand we sometimes compute about 400 statistical models / sec.

I am experimenting with Kotlin .. but it can solve some real problems for me if it works out. My front-end work leans heavily on a data frame and interactive table library I wrote in JavaScript. Moving that to a language that can support operator overloading, builders, and static type checking could make using that library much more convenient. Not to mention a lot of code that could be shared between the back and front end.