Niklas Mischkulnig

So are there exactly 2 cases that can happen (regardless of the module graph structure and how many importers a given module has)? 1. for RSC, there is always a...

Why did all hashes change? Should we maybe change the `Layer` not to hash the user_friendly_name? Or was that just because of the type change But not a big deal...

> Would a hash of the input file contents work or do we really need to use an output hash after all transformation? What's not handled with the input hash...

👍

Please also add a test case (similar to this one https://github.com/parcel-bundler/parcel/blob/v2/packages/core/integration-tests/test/mdx.js)

You need to somehow remove the functions in preserialize and then rehydrate it in postdeserialize, Babel and PostCSS are similar: https://github.com/parcel-bundler/parcel/blob/4aa4acc4e5da7ae086136a455f7506eeb7972cdb/packages/transformers/postcss/src/PostCSSTransformer.js#L19-L29 https://github.com/parcel-bundler/parcel/blob/4aa4acc4e5da7ae086136a455f7506eeb7972cdb/packages/transformers/babel/src/BabelTransformer.js#L10-L20

> We'd need to make our own parcel specific MDX config syntax We did something similar for postcss anyway. ```js const images = require('remark-images') const emoji = require('remark-emoji') module.exports =...

> I think we should handle exports the same as with Rust - make it seamless without having modulePromise and instancePromise. Is there a case where you need to pass...

Also found it here: https://www.assemblyscript.org/exports-and-imports.html#imports So I guess we have to provide some why to pass them in. This is also what I dislike about the proposal for importing Wasm...

I think Rollup and Parcel differ enough that it makes more sense to reimplement the features instead of a 1:1 port. I've made a minimal version work (no automatic JS...