I don’t want to make changes before @Cedric and I had a chance to discuss the next steps, but I don’t see why we can’t improve the experience, if a lot of the users have issues with it.
i’ll summarize the next steps I see:
- Make sure we have a dependency-free UMD package (i.e. no fs and no path).
- Make the UMD package the “main” library of the recast package
- Create an ESM-Friendly version of the package
- Make the esm package the “module” reference in package.json
- Release the ASM version in the package as a separated package (UMD at first, but I don’t see why not do an ESM-ASM version as well). This should include the changes referenced just 2 posts ago.
- Update the README with the instructions on how to use it in all scenarios
Did I forget anything?