question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

What is nexus / nexus schema / nexus framework / nexus js / nexus experiment?

See original GitHub issue

Can anyone explain current and historic naming of these things?

I see this repository is called “nexus”.

I is linked with page “nexusjs”

https://nexusjs.org/

But I know that “nexus graphql framework” was called in this way and is unmaintained and now called “nexus experiment”.

I looking for “nexus schema” (without unmaintained framework) but after update of packages like “nexus plugin prisma” i see errors:

Cannot find module 'nexus' or its corresponding type declarations.

I expected that “nexus plugin prisma” will use now pure “nexus schema” without “framework” but I see imports like these

import { core } from 'nexus';

in node_modules/nexus-plugin-prisma/dist/utils.d.ts

But when I typed in google “nexus framework migration guide” I see working page:

https://nexusjs.org/docs/adoption-guides/neuxs-framework-prisma-users

that should be marked as depreciated / unmaintained

There is link to migration from nexus to nexus-schema

https://nexusjs.org/docs/adoption-guides/nexus-framework-users

but now it is called Nexus (without schema)

Screenshot from 2020-12-30 16-09-53

When in annoucment

https://github.com/prisma-labs/graphql-framework-experiment

It is called Nexus schema

Screenshot from 2020-12-30 16-10-05

Now nexus schema is depreciated:

https://www.npmjs.com/package/@nexus/schema

Screenshot from 2020-12-30 16-12-47

Sorry for this long issue, but somebody responsible for these decisions (of changes in naming) should not manage this project.

I initially loved it but now I do not want to use any tools with nexus in name because of terrible management of communication with programmers and outdated documentation.

Please imagine, how much chaos and confusion will it generate when you are searching for solution and you see materials with such many names and any of them should be matched with dates range to check what author mean by this name.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:4
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

5reactions
Syttencommented, Dec 30, 2020

Yeah this was not great and that is why I advised to stick to the @nexus/schema name. Anyway long story short:

  1. Original package was called nexus
  2. Package was renamed nexus/schema and nexus was rebranded for the framework around v0.12 if I remember
  3. Framework is abandoned and moved to nexus-experiment
  4. Nexus schema is rerenamed nexus on the v1 release

Should be better getting forward, but lots of small places remain with old names.

1reaction
jasonkuhrtcommented, Jan 6, 2021

Answered by @Sytten thanks. PRs to update old ID names are welcome if found.

Read more comments on GitHub >

github_iconTop Results From Across the Web

GraphQL Nexus · Declarative, Code-First GraphQL Schemas ...
Automatically generates and infers types based on the schema. No need to manually add annotations, Nexus can automatically infer them in TypeScript using...
Read more >
Nexus Framework Users
Hello Nexus Framework User! · Bundled Dependencies · JavaScript Support · Managed TypeScript · Development Mode · Nexus Module Discovery & Singleton Schema...
Read more >
Schema - GraphQL Nexus
This is the Nexus component guide. Here you will find concepts explained and a survey of how to use the API. If you...
Read more >
Nexus Documentation (Concepts, Reference & Guides)
Nexus builds upon the primitives of graphql-js , and attempts to take the simplicity of the SDL schema-first approach and pair it with...
Read more >
Why Nexus? - GraphQL Nexus
With Nexus, our schema and its resolvers are always defined together. Nexus also allows us to write everything in a common language. This...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found