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.

[bug] global is not defined

See original GitHub issue

Note: for support questions, please use one of these channels: stackoverflow or slack

You want to:

- [x] report a *bug*
- [ ] request a *feature*

Current behaviour

socket.io-client doesn’t work with @angular/cli @1.5.0-rc.3 because of a dependency on node.js’ global var (seems to come from has-binary2@1.0.2, but I can’t find who maintains that versions)

Steps to reproduce (if the current behaviour is a bug)

see https://github.com/angular/angular-cli/issues/8160

Expected behaviour

Setup

OS:
browser:
socket.io version: 2.0.4

Issue Analytics

State:
Created 6 years ago
Reactions:28
Comments:53 (15 by maintainers)

Top GitHub Comments

231reactions

amitportcommented, May 3, 2018

According to https://github.com/angular/angular-cli/issues/8160#issuecomment-386153833:

adding the following polyfills.ts should work in Angular@6:

// Add global to window, assigning the value of window itself.
(window as any).global = window;

In any case, this issue should not be resolved IMO, socket.io-client should either remove the implicit dependency on global, or document that a polyfill is needed (by anyone using the pre-bundled sources, not just Angular users)

(BTW where are the sources for latest has-binary2@1.0.2? maybe I could help)

29reactions

bibhas2commented, May 31, 2018