error "exports" is not defined
See original GitHub issuegetting error “exports is not defined” at @apollo/client/link/ws/index.js:
exports._type = "esm";
I see that upgrading @apollo/client to latest version (v3.6.9) fixes this by removing this line. I’m maintaining Bit, a build tool for other developers. So I want to explain to them why they need to upgrade apollo.
- what version of @apollo/client fixed it?
- is there any related issue? I can’t find any information about it
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Typescript ReferenceError: exports is not defined
I had the error "exports is not defined" coming from an imported NPM module. Changing my typescript config did nothing as I had...
Read more >ReferenceError: exports is not defined in TypeScript | bobbyhadz
To solve the "Uncaught ReferenceError: exports is not defined", add a script tag that defines an exports variable, e.g. <script>var exports = {};</script>...
Read more >How to fix ReferenceError: exports is not defined TypeScript
If you are getting the error for code that runs in the browser, try defining a global exports variable above the script tags...
Read more >Uncaught ReferenceError: exports is not defined : r/typescript
Getting this error for some dumb reason i'm sure. Uncaught ReferenceError: exports is not defined. at app.js:2. (anonymous) @ app.js:2.
Read more >Uncaught ReferenceError: exports is not defined #71 - GitHub
I'm running into that same runtime error (also using Rails + webpacker but no Typescript). I'm importing the yup resolver rather than the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@KutnerUri it shouldn’t come back as an issue, but if it does, please let us know. Given this may be hard to trace down, due to the age of the change, I’m going to mark this as done for now.
thanks, I’m ok. I just wanted to figure this out, and maybe ensure it doesn’t return.