Odtnhj

I have an application which is going to be used by individual companies. This means that, most of the time small things are going to change each time (eg.: company logo, icons, images, ...)

But there is a chance that one of them is going to ask to change one of the existing module of the app.

I'd like to create an environment in which I can safely overwrite this module without effecting the other versions.
For this I thought, maybe I could make a npm package out of the app. For this to work I'd need to solve some problems:

• Use the overwrited module
  
  For this, from this npm package i have to import files from out of the node_modules folder.

E.g:

In node_modules/app_package/src/components/Home.js

I'm importing a gallery component `import Gallery from "src/components/Gallery"

One of the company ask for a different design for this gallery (it could be anything, eg.: different authentication)

In that case I'd copy the gallery component from the npm package to src/components/Gallery.js (Note that this src folder is not the same as before)

• In an overwrited file, the import should look in to the npm package too
  
  Though I overwrite a file, it still can have dependencies in the npm package.

E.g:

In the gallery component I'm using the ImageContainer component which is located at node_modules/app_package/src/components/ImageContainer.js.

So the import ImageContainer from "src/components/ImageContainer.js first should look for it in the root folder, and if didn't found it fallback to that file in the npm package.

An npm expert could help me out on this?