# Package namespaces migration throwing an "EventEmitter" error

**URL:** <https://community.amazondeveloper.com/t/package-namespaces-migration-throwing-an-eventemitter-error/27319>\
**Category:** Bug Reports\
**Tags:** vega-libraries\
**Created:** [January 14, 2026, 7:23pm UTC](https://community.amazondeveloper.com/t/package-namespaces-migration-throwing-an-eventemitter-error/27319 "2026-01-14T19:23:10Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![amen](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@amen](https://community.amazondeveloper.com/u/amen)\
**Post date:** [February 24, 2026, 9:52pm UTC](https://community.amazondeveloper.com/t/package-namespaces-migration-throwing-an-eventemitter-error/27319/8 "2026-02-24T21:52:12Z")

</div>

Hi @Jordi_Garcia,

Thanks for your patience throughout this investigation. A few notes for your reference:

- **EventEmitter error** : Caused by an incompatible `expo` version. Fix: pin `"expo": "~[PIN]"` in your `package.json`, run a clean install, and verify with `npm ls expo`.

- **Assets folder deletion** : Your custom `clean` script in `package.json` was removing the assets directory. Remove `assets` from that script to prevent this going forward.

The updated scope migrator script (with proactive validations to catch similar issues) is now available here: [Developer's Guide: Simplifying npm scope migration with Amazon provided tooling](http://community.amazondeveloper.com/t/developers-guide-simplifying-npm-scope-migration-with-amazon-provided-tooling/20213)

Hope this helps!

---

_[View the full topic](https://community.amazondeveloper.com/t/package-namespaces-migration-throwing-an-eventemitter-error/27319)._