ReferenceError: navigator is not defined at new NgxZxingComponent about ngx-scanner HOT 8 CLOSED

I think that 172561e should do the trick. I could not test it yet. The environment to test should be based on the angular-universal-starter template.

from ngx-scanner.

I noticed that this was breaking some SSR, also this could be an error with my polyfills.

from ngx-scanner.

Try this. If it is a browser do not load anything.

E. g. this line should be moved to the ctor.

If the platform is browser the component should not do anything. Maybe a placeholder class is good for this that's functions are implemented as dummy, but has the same interface as the qr reader class.

from ngx-scanner.

E. g. this line should be moved to the ctor.

Agreed.

I reduced that behavior by checking typeof navigator before using it, but it stills buggy sometimes.

from ngx-scanner.

The first link helps how to realize if it is a browser. You don't need the navigator object for that. (navigator may be tree-shaken and the build will remove it during AOT build.)

from ngx-scanner.

I've implemented that in a new branch, but I couldn't test it in server-side yet.

from ngx-scanner.

Fixed in #78.

from ngx-scanner.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from ngx-scanner.