Comments (14)
Could you guys provide a more specific approximation of when support will be released?
If the number of ๐ here ever show it as a primary bottleneck to adoption then that would give it priority.
from graphql-framework-experiment.
Hey gang, +1 for javascript support, and thought I'd add my 2 cents.
I get the benefits of typescript, and it's great that Prisma and Nexus are written in typescript - it speeds up my development a lot!
But I don't think Nexus should be concerned about external typing and force people to use typescript (Prisma doesn't do this, nor does Nexus Schema, which I currently use). I've personally found typescript a huge pain in the arse to learn, and whilst I'd like to get around to it one day, it currently slows down my development process too much. Additionally, you might need to account for people using flow or other type checkers as well.
The only thing stopping me from using Nexus is I have to learn typescript first. It would be great if you supported javascript, that way I could learn typescript when I'm ready and have the time :)
ps. The framework looks like it'll be amazing and I can't wait to try it! Thanks for all the work you're putting into it!
from graphql-framework-experiment.
Hey @Sm03leBr00t, probably not in Q2 at least.
from graphql-framework-experiment.
Thanks for the input @ryanking1809. JavaScript will probably be supported one day, but it is a matter of priority. If many users want it then we'll do it sooner. Otherwise it might take a little longer. Either way we have no intention of not supporting JavaScript right now.
While it may seem simple we actually leverage the TS AST for quite a few features, and not just type safety ones e.g. #833.
Maybe Nexus for JS would use Babel for its AST work. Maybe we could use Babel for the TS parts too.
Another approach could be JS without 100% feature parity with the TS version (such as aforementioned #833).
from graphql-framework-experiment.
what features will be dropped from reading #833
That one is about, all modules that import nexus
get automatically added to the final bundle. We use the AST to figure this out. Frankly we could implement this one with just regex if we had to. And again Babel is another way.
from graphql-framework-experiment.
Hey gang, +1 for javascript support, and thought I'd add my 2 cents.
I get the benefits of typescript, and it's great that Prisma and Nexus are written in typescript - it speeds up my development a lot!
But I don't think Nexus should be concerned about external typing and force people to use typescript (Prisma doesn't do this, nor does Nexus Schema, which I currently use). I've personally found typescript a huge pain in the arse to learn, and whilst I'd like to get around to it one day, it currently slows down my development process too much. Additionally, you might need to account for people using flow or other type checkers as well.The only thing stopping me from using Nexus is I have to learn typescript first. It would be great if you supported javascript, that way I could learn typescript when I'm ready and have the time :)
ps. The framework looks like it'll be amazing and I can't wait to try it! Thanks for all the work you're putting into it!
@jasonkuhrt I agree with @ryanking1809; having to learn TS first is a real pain for people who already built their apps entirely JS.
After spending more time examining the examples in prisma-examples/javascript/
and prisma-examples/typescript/
, I realized that it would be faster for me to learn TS than to build a manual JS workaround myself. I'm sure they are other people besides us two who have found themselves in similar situations.
Saying this is a pain is to say the least, as I was getting ready to deploy my app and now realize that I have to spend my entire day having to learn some TS to be able to implement a deployable fullstack Prisma, GraphQL Nexus, and Next app.
from graphql-framework-experiment.
Is this something anybody works on?
from graphql-framework-experiment.
What do you mean Q2? Sorry, I am just a beginner, I love the way nexus works, but typescript for me is just a pain in the ass, excuse my language. Feel free to reach out @jasonkuhrt via email :[email protected]
from graphql-framework-experiment.
@Sm03leBr00t I mean the months of April/May/June.
I hear you, its definitely a learning curve, and a tradeoff. In case it helps we have some curated content to onboard with TS here: https://www.nexusjs.org/#/getting-started/onboarding?id=pre-requisites
from graphql-framework-experiment.
@jasonkuhrt Thanks mate, hope to hear more from you
from graphql-framework-experiment.
Question about this recently graphql-nexus/nexus#773
from graphql-framework-experiment.
All good, thanks @jasonkuhrt. It's hard for me to tell what features will be dropped from reading #833 but if it's easy to do, could be worth testing.
from graphql-framework-experiment.
Yes, having to work all the way up to deployment with JavaScript and then realizing you must convert your codebase to Typescript is excruciatingly painful.
Could you guys provide a more specific approximation of when support will be released?
If not, what kind of software help is needed, and perhaps the community can swoop in to save the day and help you release JS support sooner rather than later?
Also happy to privately share my email for updates!
from graphql-framework-experiment.
Added a new label to help track JS issues lang/js
.
from graphql-framework-experiment.
Related Issues (20)
- TS error with inputObjectType default value when using with list=true
- write test for build showing esnext module type works
- nexus:dev reflection failed HOT 8
- Force include directories in build
- Field in interface not get type generated
- Roadmap is empty HOT 3
- @nexus/schema return wrong error object shape
- Empty errors in production environment
- queryField and mutationField not generating types when used in makeSchema HOT 1
- On main page there is broken link to new handbook of typescript
- No source map when debug
- Add connection to ContextAdderLens
- Missing multipart field โoperationsโ (and other related errors) HOT 1
- TypeError: cookieParser is not a function after upgrading to 0.26.1 HOT 1
- Build error using pnpm
- Parallel testing causes multiple servers on the same port, resulting in jest hanging and failing unpredictably
- unhandledRejection
- Announcing the Sunsetting of Nexus Framework and a New Focus on Nexus Schema
- How do You use socket.io
- [email protected] does not support @prisma/[email protected]
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graphql-framework-experiment.