Exposing Modules Imported from Nested Path about expose-loader

[alexander-akait]

Close in favor #79

[KutnerUri]

sorry but #79 does not seem related.
I am encountering the same problem: trying to expose a package that is consumed as is, and also as nested files.

In my example, grapql is consumed as:

import graphql from 'graphql';
import { ExecutionResult } from 'graphql/execution/execute';
import { DocumentNode } from 'graphql/language/ast';
import { parse } from 'graphql/language';

this makes my current loader irrelevant:

test: require.resolve('graphql');
loader: 'expose-loader',
options: {
  exposes: "graphql"
}

this will expose window.graphql correctly, but completely ignore internal files like graphql/language.

I wanted something like this:

{
  descriptionData: { name: 'graphql' },
  loader: 'expose-loader',
  options: {
    exposes: ['graphql', '__$internalFilepath']; // but this syntax does not exist
  }
},

@alexander-akait - any thoughts?