We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, would it be possible to offer ESM-friendly packaging for frameworks wishing to support _hyperscript?
The goal is to be able to pass the build system something like export { default } from "hyperscript.org";
export { default } from "hyperscript.org";
Or with advanced features,
export { default, workers, socket, eventsource } from "hyperscript.org";
such that the build system can bundle it in into one file, and hyperscript's side-effecting the DOM can still work.
It would typically involve using the exports field in package.json.
exports
package.json
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, would it be possible to offer ESM-friendly packaging for frameworks wishing to support _hyperscript?
The goal is to be able to pass the build system something like
export { default } from "hyperscript.org";Or with advanced features,
export { default, workers, socket, eventsource } from "hyperscript.org";such that the build system can bundle it in into one file, and hyperscript's side-effecting the DOM can still work.
It would typically involve using the
exportsfield inpackage.json.The text was updated successfully, but these errors were encountered: