@dnolen the stuff you just added for the module loader could potentially be used to combine the load+resolve

eg. instead of remembering which module a namespace is in directly load a def

(load/special-invoke 'some.ns/fn foo bar args)

or (load/resolve 'some.ns/fn (fn [the-thing-it-resolved-to] ...))

just an idea not sure if useful yet

but it sure would be nice if you don’t have to remember which module a namespace is in since that might change over time

@thheller that’s a pretty nice idea, will think about that

oh such fun … react@next v16 beta is out, index.js looks like

'use strict';

if (process.env.NODE_ENV === 'production') {
  module.exports = require('./cjs/react.production.min.js');
} else {
  module.exports = require('./cjs/react.development.js');
}

well .. I guess it still works. only that :none also loads the minified version and closure has to kill the dev version …

guess its time to write the process.env.NODE_ENV preprocessor

has anyone seen that pattern before? seems like a weird thing to do, wonder if its common?

Not common afaik