Update sbt-scalajs, scalajs-compiler to 1.0.1

[scala-steward]

Updates

• org.scala-js:sbt-scalajs
• org.scala-js:scalajs-compiler

from 0.6.32 to 1.0.1.

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Have a fantastic day writing Scala!

Ignore future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-js" } ]

labels: library-update, semver-major

[larsrh]

Blocked on machinist. Needs a similar PR as typelevel/cats#2925.

[cosmin33]

Why is that ? Machinist can't work on scalajs 1.0 ?
In the cats PS the problem with machinist was Dotty, not scalajs 1.0 as I understand...

[cosmin33]

I managed to update spire for scalajs 1.0.1. But machinist dependency being an archived project I had to modify and publish locally. This is the script to locally publish the current spire snapshot for scalajs 1.0.1:

git clone https://github.com/cosmin33/machinist.git
cd machinist
sbt publishLocal
cd ..
git clone https://github.com/cosmin33/spire.git
cd spire
sbt publishLocal
cd ..

I can make a PR but I don't know how to proceed with machinist. Any ideas ?
In the mean time the forked repos are there for future reference.

[erikerlandson]

What is spire's roadmap for dealing with archival of machinist?

[erikerlandson]

machinist effectively consists of a single file: Ops.scala - if the machinist project is dead, but spire depends on it then...

@denisrosset to unblock migration to scalaJS 1.x, I'd propose moving Ops.scala back into spire. It's only used in the macros project for Syntax.scala

[denisrosset]

@erikerlandson Totally agree. I'm doing that.