Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Inconsistent pairing of sbt-typelevel and scalajs

Open Beginner friendly
#929 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
scala

Research direction

Look at the project's build files to find where the sbt-scalajs plugin version is defined. The issue suggests updating from version 1.13.2 to 1.20.1. Check for any version compatibility constraints with sbt-typelevel and Scala.js. Run the build locally to verify the fix resolves the dependency error.

Written by the indexing model from the issue text.

Description

bug

Using: addSbtPlugin("org.typelevel" %% "sbt-typelevel" % "0.8.7")

In Github Actions, and the Submit Dependencies (ubuntu-22.04, temurin@8) job the following error occurs

[warn] 	Note: Unresolved dependencies path:
[error] sbt.librarymanagement.ResolveException: Error downloading org.scala-js:scalajs-compiler_2.13.18:1.13.2
[error]   Not found
[error]   Not found
[error]   not found: /home/runner/.ivy2/localorg.scala-js/scalajs-compiler_2.13.18/1.13.2/ivys/ivy.xml
[error]   not found: https://repo1.maven.org/maven2/org/scala-js/scalajs-compiler_2.13.18/1.13.2/scalajs-compiler_2.13.18-1.13.2.pom
[error] 	at lmcoursier.CoursierDependencyResolution.unresolvedWarningOrThrow(CoursierDependencyResolution.scala:350)

Workaround: Adding the following to the plugins of the project, seems to do well.

addSbtPlugin("org.scala-js" % "sbt-scalajs" % "1.20.1")

Solution: A PR that changes

addSbtPlugin("org.scala-js" % "sbt-scalajs" % "1.13.2")

to

addSbtPlugin("org.scala-js" % "sbt-scalajs" % "1.20.1")

Only issue is I don't know what kind of changes that would cascade.

Dominant language
Scala
Stars
185
Forks
62
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from typelevel/sbt-typelevel

All issues in typelevel/sbt-typelevel

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.