Skip to content

Conversation

@EdwardMoyse
Copy link
Collaborator

Unfortunately this does not work yet.

When I do yarn start I get

node:worker_threads - Error: Module build failed: UnhandledSchemeError: Reading from "node:worker_threads" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.

but opening here in case anyone has any ideas what I need to change?

cc @9inpachi @sponce @AlphaAbdo @DamianArado

@EdwardMoyse
Copy link
Collaborator Author

 YN0001: │ cypress-plugin-snapshots@git+ssh://[email protected]/meinaart/cypress-plugin-snapshots.git#commit=a8bd88380db56905f5df6fe27cb4eddb7b809b9e: Failed cloning the repository
  ➤ YN0001: │   Repository URL: ssh://[email protected]/meinaart/cypress-plugin-snapshots.git
  ➤ YN0001: │   [email protected] Error: Permission denied (publickey).
  ➤ YN0001: │   Fatal Error: Could not read from remote repository.
  ➤ YN0001: │   Exit Code: 128

No idea why this works locally but not here... To be continued.

@NikhilSharma201
Copy link

I ran into the same SSH error while testing this branch:

cypress-plugin-snapshots@git+ssh://[email protected]/meinaart/cypress-plugin-snapshots.git
Fatal Error: Could not read from remote repository.

Looks like the dependency is being pulled via SSH, which fails without GitHub SSH access. Would switching to an HTTPS Git URL or publishing a version to npm help make installs more contributor-friendly?

@EdwardMoyse
Copy link
Collaborator Author

EdwardMoyse commented Oct 29, 2025 via email

@NikhilSharma201
Copy link

Got it, happy to help test any workaround or patch once it's ready. Let me know if you'd like me to try a fork or alternate setup.

EdwardMoyse and others added 7 commits November 3, 2025 18:04
…stic EventEmitter

- Created framework-independent EventEmitter class to replace Angular's EventEmitter
- Removed Angular dependency from phoenix-event-display library
- Fixed Jest configuration (jest.conf.js -> jest.conf.cjs, corrected setup paths)
- Added comprehensive mocks for three.js ESM examples to resolve test issues
- Created test suite for EventEmitter with full coverage
- All tests now passing (345/345 tests, 83/83 test suites)

This change makes phoenix-event-display truly framework-agnostic and improves
the library's architecture by removing the Angular framework dependency.
feat(event-display): Remove Angular dependency from phoenix-event-display and fix phoenix-ng test infrastructure
Comment on lines +3 to +17
import {
BufferGeometry,
Material,
Object3D,
Camera,
Scene,
WebGLRenderTarget,
WebGLRenderer,
EventDispatcher,
Vector3,
MOUSE,
TOUCH,
Spherical,
Vector2,
} from 'three';
@EdwardMoyse
Copy link
Collaborator Author

Locally at least, this still seems to be failing with:

node:worker_threads - Error: Module build failed: UnhandledSchemeError: Reading from "node:worker_threads" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.

@deveshbervar
Copy link
Collaborator

Hi @EdwardMoyse I’d like to work on this issue.
I can test the branch locally and start looking into:

  1. Replacing the SSH-based dependency for cypress-plugin-snapshots with an HTTPS or npm version.
  2. Investigating the Webpack “UnhandledSchemeError: node:worker_threads” issue in Angular 20 builds.
    If this direction is helpful, I can begin contributing fixes or suggestions.

Please let me know if there are any specific tasks I should start with.

@EdwardMoyse
Copy link
Collaborator Author

@deveshbervar that would be amazing. Feel free to trash this MR and start again if you prefer. I'll assign the related issue to you.

@deveshbervar
Copy link
Collaborator

Thanks a lot for the invite, @EdwardMoyse!
Really appreciate it — I’ll start from a clean branch and reopen the upgrade as a new MR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants