Uncaught Error: Module "events" has been externalized for browser compatibility. Cannot access "events.EventEmitter" in client code

Question

I don't know what's going on I am making a frontend using vite + react for my mern project and suddenly starts encountering this error.

Error: Module "events" has been externalized for browser compatibility. Cannot access "events.EventEmitter" in client code.

git repo link : https://github.com/Gaurav200247/E-Book-Store-Mern-Project

Catchings

Hi! Could you figure it out? I'm stuck with the same issue. – Quack

not able to figure it out, but i'm using localstorage (JS) in my code i just removed that lines of code. The error gone automatically. – Catchings

Answer 1

Had the same issue, the events module was in sub-dependencies, I added it manually by npm install events, then the issue disappeared.

Silkworm

Did you import anything afterwards? – Samuelsamuela

No, it couldn't find that module somewhere inside of a dependency. After manual installation that becomes available. – Silkworm

for me error is not resolved even after installing events , with npm i events – Glume

Answer 2

Make sure that:

1. You are importing the correct library in your code.
2. The library you are attempting to use is directly installed in your project, libraries available as sub-dependencies will not work.

Suzy

Answer 3

it happens when mistakenly a backend package gets imported in frontend

Blush

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center. – Ikeda

Answer 4

I have faced this problem when I have installed jsonwebtoken in client side. You need to avoid install server side packages or modules in client side to avoid this error or warning.

Tomkin

Answer 5

In case you are using Angular and stumble upon this page, know that the other solutions are temporary. This might be an issue caused by the auto importing of the package by IDE, say vsCode.

The other solutions mention just installing the package. However, what you need to check is if you're importing the eventEmitter from the right library.

Check that it is

import { EventEmitter } from '@angular/core';

and NOT

import { EventEmitter } from 'stream';

The other solutions mention running npm i or installing the package, but in turn, you are just installing the stream package, which is probably not needed.

Gersham