How to improve nested requires?

We would like to figure out how to improve requiring modules.

e.g. take a look at this - we have to go back in the folder tree to be able to require the logging module.

The same problem exists in our test env, see.

global require function

One option could be to add a global.requireSomething fn, which is able to read modules from a defined root path.

e.g. requireRoot('services') - would require a module from the core/server folder. e.g. requireLib('errors') - would require a module inside core/server/lib

other options?

Wait that Node supports import/export and a similar module like ember-resolve. So you can do:

import * from 'ghost/services' - that would be so cool 🙊

[ernstwi]

In case it could be useful in future, here’s a script to rewrite the require paths using the current directory as root.

[kirrg001]

@ernstwi Hey, thanks for coming back. I’ll reply tomorrow 👋