|
|
|
|
|
by creatable
1088 days ago
|
|
What I specifically meant is that the "type" property can impact runtime evaluation as per the spec, however it's implied to be used specifically for impacting runtime evaluation based on a file's type. Say I have a module in a language that transpiles to JavaScript based off of the "type" property. In Bun, I would not be able to use any functions exported by it as a macro because the "type" property is being used for defining the module as a macro. That's the specific issue I have. |
|
This turns what looks like a function call in the importer into something like macro expansion (it doesn't look like actual macros though).