Jayden Seric

Thanks for the revelation, although this is a real headache to solve elegantly 😓 Bundling published packages is an antipattern, and you can't have `require()` inside ESM for a conditional...

Is `optimizeForSpeed` even worth it? What exactly are the benefits? I might just continue to publish `device-agnostic-ui` components and styles transpilled with it `false`, and in the Next.js setup instructions...

Here is an example of the difference between transpiling published components without and with `NODE_ENV=production`… For this component: https://deviceagnosticui.com/components/Blockquote Here is without: ```js export var stylesBlockquote = { styles: React.createElement(...

Perhaps you misunderstood the suggestion... It would be impossible to support importing non `optimizedForSpeed` styles for use in a production build, because it is hard to cut up a style...

@giuseppeg I got started on a PR a few weeks ago but had to move onto other stuff. Sorry, but I'm now out of time and money to work on...

Strange, I get one.

Here is the root cause: https://github.com/browserify/detective/issues/45 `detective` is used by `module-deps` here: https://github.com/browserify/module-deps/blob/v6.1.0/index.js#L506 And I think `module-deps` is used indirectly here: https://github.com/documentationjs/documentation/blob/v8.0.0/src/input/dependency.js#L25

This seems to only happen when the source file has a `.mjs` extension.

The babelify transform is not transforming source from .mjs files for some reason. I've created a dirty noop transformer to log out what is happening: ```js const through = require('through2')...

Idea: Maybe we need to use the [`mdeps` `resolve` option](https://github.com/browserify/module-deps#var-d--mdepsopts), because the default node-browser-resolve in turn [uses a pinned, old version of resolve](https://github.com/defunctzombie/node-browser-resolve/pull/85), which itself is [out of touch with...