I've started fleshing out a repro for @raquo's issue here: scalameta/mdoc#455
Sadly the naive approach doesn't seem to work, tests are still passing
I have another approach of intercepting a CLI command one of my tool makes and trying to make it match the reproducible in the issue.
I think the closest we will get is to get a CLI reproducible: https://scalameta.org/mdoc/docs/js.html#command-line
Admittedly, it's quite hairy and that's why I wanted to reproduce it in tests first.
Is this blocking you from upgrading laminar to 1.3x (asking because I thought you wanted to postpone that)
git release 1.2.4script like this
❯ cat `which git-release` set -eux version=$1 git tag -af "v$version" -m "v$version" && git push -f origin v$version
crossScalaVersionsto cross-build the
docssbt project against multiple versions, but that would give you independent copies of the entire website
If you are deploying to GitHub pages, make sure to run yarn deploy instead of yarn publish-gh-pages script.
sbt docusaurusPublishGithubSomethingCommandwon't work
Use Docusaurus v2 if:
✅ You want a single-page application (SPA) with client-side routing
I'm having an issue moving from
mdoc on a project using Scala 2.12.8:
addSbtPlugin("org.scalameta" % "sbt-mdoc" % "2.2.18") and
addSbtPlugin("org.scalameta" % "sbt-mdoc_2.12" % "2.2.18") but both failed:
The first one looks for:
and the second one looks for:
https://repo1.maven.org/maven2/org/scalameta/sbt-mdoc_2.12_2.12_1.0/2.2.18/sbt-mdoc_2.12-2.2.18.pom maybe because of coursier/coursier#1950
(while the correct URL is https://repo1.maven.org/maven2/org/scalameta/mdoc-runtime_2.12/2.2.18/mdoc-runtime_2.12-2.2.18.pom)