Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected token in @urql/[email protected] #1172

Closed
protometa opened this issue Nov 19, 2020 · 2 comments
Closed

Unexpected token in @urql/[email protected] #1172

protometa opened this issue Nov 19, 2020 · 2 comments
Labels
bug 🐛 Oh no! A bug or unintented behaviour.

Comments

@protometa
Copy link

urql version & exchanges: @urql/[email protected]

Steps to reproduce

  1. npm i @urql/[email protected]
  2. node -r @urql/exchange-populate

Expected behavior

Loads module

Actual behavior

SyntaxError: Unexpected token '}'
    at wrapSafe (internal/modules/cjs/loader.js:979:16)
    at Module._compile (internal/modules/cjs/loader.js:1027:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1217:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:446:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:74:3)
    at internal/main/repl.js:19:1
@protometa protometa added the bug 🐛 Oh no! A bug or unintented behaviour. label Nov 19, 2020
@kitten
Copy link
Member

kitten commented Nov 19, 2020

I believe this is related to what's been fixed in 1714076

This hot fix addressed a build issue that I only discovered after releasing several updates to packages which corrupted some releases. It seems I missed that it also affected @urql/exchange-populate so to fix a re-release is necessary.

That being said, no necessary changes to use the package were introduced and in the meantime 0.2.0 will still work.

So #1149 still takes precedence over this issue

@kitten
Copy link
Member

kitten commented Apr 28, 2021

This will be fixed by #1570 although usage of the populateExchange is not exactly recommended (and still experimental/early) until #964 lands.

@kitten kitten closed this as completed Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Oh no! A bug or unintented behaviour.
Projects
None yet
Development

No branches or pull requests

2 participants