-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
esnext problem #160
Comments
Can you throw up a repro repository or Codesandbox? I’ll debug it. |
that would be really appreciated https://github.com/basz/rpc-test |
exports doesn't exist in the browser. Can this be distributed as ESM? |
Sorry I wasn’t clear. Now change ***@***.***/package.json to "rpc-websockets": "7.11.0"On 1 Jun 2024, at 08:14, Steven Luscher ***@***.***> wrote:
I tried your repro, and unfortunately couldn't break it.
sudo n lts # Install Node LTS
rm pnpm-lock.yaml # Your lockfile was giving me trouble
pnpm i
pnpm start:dev
image.png (view on web)
image.png (view on web)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
The solution was the most annoying thing possible. Rename everything to #161. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the changed esnext compile thing from 1.11.0 is breaking usage for me in an EmberJS app
That file ends up as (indeed without
exports
)Probably an config thing but if anyone sees what it could be please let me know
The text was updated successfully, but these errors were encountered: