ESM discussion #94
Open
ESM discussion #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm with the same problem as you @binarymist. I wasn't planning moving away from Sywac during the migration 😕 |
75 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I realised when I was moving my projects from CJS to ESM that sywac is a blocker. I think 55f2ea8 may be all I need in order to move forward unless I hit other problems. ESM can consume CJS without to much fuss, but the other way around introduces a lot more friction, and since sywac consumes the command modules which are now in ESM it becomes a problem.
@nexdrew: What are your plans for migrating sywac to ESM? Are you thinking of:
I'd be happy to help with the ESM effort, as I have a production CLI depending on sywac.
Thanks.