Skip to content

Fix broken NPM bundle by publishing in ES-Module format #1958

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

elikoga
Copy link

@elikoga elikoga commented May 6, 2025

Closes #1943
Repeat of #1944 with different head branch

Testable by placing "@novnc/novnc": "npm:@elikoga/[email protected]", in package.json

Uses exports in package.json to make sure that old imports still work

This one incorporates the review requests in the previous PR by simply dropping the conversion step using babel.

CI Passes in my repo

@CendioOssman
Copy link
Member

Please don't open a new PR as that means it is more difficult to see all the context. You can just adjust the existing one with your changes.

@elikoga
Copy link
Author

elikoga commented May 6, 2025

@CendioOssman sadly github does not allow changing the head branch of the PR. Your request is to history-rewrite my original PRs head (master)? I can do that but for me it makes it more difficult to understand the context in the future.

@elikoga
Copy link
Author

elikoga commented May 7, 2025

image

Yeah I literally can't reopen the other PR or this one.

@samhed samhed reopened this May 12, 2025
@samhed
Copy link
Member

samhed commented May 12, 2025

Continue here then, strange behavior by GitHub..

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.

noVNC cannot be bundled due to top-level await in browser.js
3 participants