Mika

I have the same issue. using `-x` flag doesn't help either, because that only includes the binary and not which flags to use.

> but you're wrong about your solution being horrible Haha, agree to disagree ;-) > `import /* from */ './my-custom-element.js'` I'll have something ready once I have some time to...

Oh, and just to be clear: this will be for web projects only. There is no package.json file, no dependency management, etc.

Thanks for the pointers! I might start work on this already tomorrow if nothing else comes up. I think we also need a configuration option to enable/disable this feature. Some...

Confirmed that specifying them manually in config solves the issue. .importjs.js ``` module.exports = { namedExports: { 'react': ['useState', 'useEffect', 'useContext', 'useReducer', 'useCallback', 'useMemo', 'useRef', 'useImperativeMethods', 'useLayoutEffect'] } } ```

Well, not at the time when I created this issue. I have since stopped using React, so I don't know if it has been solved since then.

Same issue here. Only `http` seem to work for name, meaning I can't have more than one cloud function. That makes serverless useless. Does anyone know a workaround? Seeing how...

Would it be possible to add HTTP2 push support, and an option to disable bundling? With bundling, we get this issue: Imagine having `A.js` imports `C.js`. We run an SPA....

I can also reproduce this.

Bumping this thread. Seems no activity going on to fix this? Anyone?