Graphql-playground: Urgent, Prisma playground broken, Uncaught SyntaxError: Unexpected end of input

Created on 11 Feb 2019  路  19Comments  路  Source: graphql/graphql-playground

I'm using a Prisma server, and I'm using the playground included in my browser. I'm getting the following error: Uncaught SyntaxError: Unexpected end of input

The error is being thrown from the following file:

http://cdn.jsdelivr.net/npm/graphql-playground-react/build/static/js/middleware.js

All of my GraphQL playgrounds are broken across localhost and a few live Prisma server instances

bu0-needs-info

All 19 comments

Could you provide more info? Everything works fine in my end.

I'm using Prisma version 1.21.1, I have a Prisma server running on an aws instance. In fact, you can just go here: https://prisma.staging.jillsoffice.com/

Open up the terminal and you can see the issue.

For me is working fine, I can't access your endpoint, because it's protected by a secret.

There is no error in your console?

You shouldn't need my secret to see that the error is being thrown. The error is throwing in Chromium and Firefox for me, Chromium 71 and Firefox 64

Nothing

Are you going directly to https://prisma.staging.jillsoffice.com in your browser? I can't even get that screen to load that you have there, I've tried on multiple browsers and another computer

The problem doesn't seem to be with my Prisma server, but with one of the dependencies loading over a cdn. I have changed nothing that should be related with my code, I think the cdn has broken something

@Huvik I can confirm this.

image

I tested clearing cache even different browser but the problem persisted.

@pantharshit00 is the error also coming from the http://cdn.jsdelivr.net/npm/graphql-playground-react/build/static/js/middleware.js file? If yes, can you copy/paste its contents here?

I tried firefox, safari, brave everything without cache. Maybe something went wrong with CDN.

@MartinKolarik Yes that is where the error is coming from. You want the contents of the file pasted here? You can click the link and see the contents. Or do you want the contents of the error?

I think it is a problem with the cdn, how do we find who can fix that? Also, why is this dependency being loaded over a cdn, and not installed along with all other dependencies with npm? It doesn't look like the cdn is allowing us to lock down a version.

For me and @Huvik the file loads fine, so yes, it would help if you could upload/screenshot the exact response.

I think it is a problem with the cdn, how do we find who can fix that?

If it's a problem with the CDN, me 馃槃

I think it is a problem with the cdn, how do we find who can fix that?

You can fix that using cdn option in playground middleware.

Also, why is this dependency being loaded over a cdn, and not installed along with all other dependencies with npm?

We are using CDN for middlewares, because we want to ship all latest version with playground without updates. You can always specify what version of the playground you want to use. There is a lot of settings you can play with it.

@lastmjs It loads fine for me now after a hard reload.

@MartinKolarik The file was giving nothing at first (I am in Asia region btw).

After a couple of hard reload it works fine again

I am closing this issue because it's not related to the playground, there is a workaround to use different CDNs or even local package version. Like i pointed out few messages up. If its still problem please ping here.

It's working again for me :)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

iagobruno picture iagobruno  路  16Comments

tlvenn picture tlvenn  路  15Comments

jazzzz picture jazzzz  路  38Comments

alex996 picture alex996  路  15Comments

gajus picture gajus  路  19Comments