Support for transpiling imports with assert {type: "json"} to use the old native way of node:fs ?

[renhiyama]

Consider looking at this code: https://deno.land/x/emoji@0.2.1/emoji.ts?source
It has assert, which crashes sucrase:

The 4th line has assert.

[alangpierce]

@renhiyama thanks for the report! I filed a tracking issue a while back as #566 , but I know this syntax is becoming more common, so definitely seems time to add better support. Could you clarify more specifically what you mean by "the old native way of node:fs"? Is there another transpiler that has the behavior you want that I could model the implementation off of?

I think the behavior I'd be most comfortable with is this:

• When targeting CJS (when imports is specified as a transform), the import becomes a require as usual and the assert {type: "json"} is ignored/removed. This should work with node because require handles JSON files automatically.
• When targeting ESM (when imports is not specified as a transform), the import assertion is passed through as-is, so the output code has the assert { type: "json" };. I just confirmed that this works on node 16+ when using node's native ESM support.

Would that work for your use case?

[renhiyama]

Oh i didn't knew it was supported in nodejs v16! Yea then we can continue with what you said above! (I didn't test a json import but I remember doing it last year) looking forward for the fix since a lot of deno modules use that and I need a way to get them too!

[renhiyama]

hey @alangpierce , when are you publishing a new version of sucrase so I can start using it in my projects?

[alangpierce]

Just released as 3.27.0, let me know if you see issues!

[renhiyama]

Worked!

Cheers 🎉