-
Notifications
You must be signed in to change notification settings - Fork 10
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
ESM support for all Yivi packages #15
Comments
Hi @ericfennis, thanks for the suggestion. We are planning transferring to the import syntax, but I can't say in advance when we'll get this done. Switching to Typescript requires a bigger effort which we won't be able to do anytime soon, unless you want to get your hands dirty of course ;) |
Any updates to this? We are switching our apps to use import maps and Yivi is the only dependency that still requires us to use webpack. When can we expect ES module support for Yivi? |
@mlangenberg Unfortunately not anytime soon since it's all hands on deck with other high priority developments at the moment. Of course it is much appreciated if you could help us out by adding ES module support and submitting this as a PR:) |
@bobhageman We’ve followed up with a PR to add ES module support. It would also be appreciated if this could get reviewed. |
Hi @mlangenberg, and @ericfennis, firstly: thanks for your effort. |
We tried to use these frontend packages with our frontend using Vite.
But we have some problems with building, because of the lack of ESM support.
We currently have a workaround but it is not great.
I noticed in all the packages the
require()
imports are used, which is not very future-proof since most new frontend builders and javascript community already shifted to theimport
syntax. Also using the ECMA script is recommended by all build tools, see webpack documentationIs it possible to switch to ECMA Script syntax or maybe even typescript.
Here is a nice blog article about publishing modern NPM package: https://snyk.io/blog/best-practices-create-modern-npm-package/
The text was updated successfully, but these errors were encountered: