npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

relay-compiler-language-scalajs

v0.41.0

Published

A compiler tool for building GraphQL-driven Scala.js applications.

Downloads

262

Readme

relay-compiler-language-scalajs

The purpose of this project is to generate Scala.js bindings for the relay-compiler. Typically, the relay-compiler generates flow bindings along with the compiled queries. This project replaces that generation and outputs js.native traits instead. It should work on most "normal" gql features. If I personally run across something not supported I try to add it, but it is by no means totally complete.

This project uses flow because it's what Relay uses, and it's better than raw javascript.

It uses artifactDirectory to generate all the source files in the same package. So it's a big flat package repository in the same directory. This is controlled by (resourceManaged in Compile).value / "relay-compiler-out /" in sbt terms.

Versions

  • 0.32.x - Relay 11.0.2
  • 0.25.x - Relay 10.1.2
  • 0.22.2 - Relay 6.0.0
  • 0.20.1 - Relay 2,0,0
  • 0.11.0 - Relay 1.6.2
  • 0.9.0 - Relay 1.5.0
  • 0.8.2 - Relay 1.4.0

Example

$ ./node_modules/bin/relay-compiler --language scalajs --src example/src/ --schema example/schema.graphql --artifactDirectory example/out

Features

  • Handle names elegantly by scoping them to the companion object.
  • Provides two ways to customize the output
  • @scalajs(extends: String) This can give you a parent class to mixin. It's your job to verify it.
  • @scalajs(useNulls: Boolean) this can give you finer control on using A | Null on a Fragment, field or inline fragment.

Example

Looking at the sbt tests is the best way to get a handle on how things work.

Basic Test

Dev

Build with:

yarn build

Testing

Go to node-example and run:

yarn iterate

Debugging

First build and then use the relay-compiler Run Configuration in IntelliJ.

Alternatively, modify iterate.sh to:

node --inspect brk

Then run this and attach a debugger.