Julien Richard-Foy

Thanks for reporting. This is funny, I have no idea what’s going on here… The source is a plain markdown file: https://raw.githubusercontent.com/scalacenter/scalajs-bundler/master/manual/src/ornate/cookbook.md Maybe Ornate is getting crazy?

I think the “scalajs-bundler way” of doing that would be to reference an object annotated with a `@JSImport("./some-file.js", JSImport.Default)` somewhere in your code instead of using `jsDependencies` and then `managedResources...

Thanks for sharing your workaround @AlexITC! However, I think it would be better if we could fix the root cause of the problem instead. I think the issue should be...

I think the best path forward would be to upgrade to CodeMirror 6, which does support LSP (see https://github.com/furqansoftware/codemirror-languageserver), which could communicate to the build server started by scastie. A...

But that’s an sbt-plugin. You intend to always add it to Scala.js projects in Scastie?

So far we didn’t provide a backward compatible API (we broke backward compatibility a lot of times). It means that if at some point you want to upgrade the version...

Maybe a friendlier way to show the errors would be to use the lining features of CodeMirror: https://codemirror.net/examples/lint/

Thank you for the suggestion! Once the specification for configuration directives is settled, we could consider working on this issue. One challenge is that currently we assume an `sbt` build...

Feature-wise, there is no need to continue using sbt. Everything we use sbt for, we will be able to use scala-cli instead. That being said, we may want to still...

Isn’t it too early to use these new Java features?