Hush webpack warnings when blueprint is not installed

[nomcopter]

Perhaps switching to require.resolve is quieter https://stackoverflow.com/a/15303236

[iAL-Ahmed]

@nomcopter Thanks for making this issue. I was just about to make an issue asking if we could either get rid of the webpack warnings or find some way to make blueprint more shakable.

[nomcopter]

Hmm.. Nope. That didn't work. Although based on some quick Googling it looks like a pretty common and hard-to-avoid error obnoxiously: webpack/webpack#7713 (comment)

[filipkaniatest]

Should we have this reopened? The issue persists

[nomcopter]

@filipkaniatest I don't think there is anything that can be done in react-mosaic. All I could find seemed to suggest that the only way around it seems to be using warningsFilter in one's webpack config.

[mejackreed]

We do it using the webpack ignore plugin: ProjectMirador/mirador#1871

[gunn4r]

We tried the webpack ignore plugin but it adds significant overhead to the build time. Using the warningsFilter seemed to work a much better with little impact on the build time.

Though it does result in webpack showing Compiled with warnings but then not showing the warnings (obviously since we filtered them).

Would be great to eliminate this issue entirely.

[stevemk14ebr]

This fails the build on parcel2, removing the require.resolve's fixes the build. This issue should be re-opened as it introduces a bug when using parcel:

🚨 Build failed.
@parcel/packager-js: `require.resolve` calls for excluded assets are only supported with outputFormat: 'commonjs'
/home/steve/repos/Aster/src/client/node_modules/react-mosaic-component/lib/util/OptionalBlueprint.js:32:9
  31 |         // https://github.com/nomcopter/react-mosaic/issues/109
> 32 |         require.resolve('@blueprintjs/core');
>    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  33 |         require.resolve('@blueprintjs/icons');
  34 |         (_a = require('@blueprintjs/core'), Classes = _a.Classes, OptionalBlueprint.Icon = _a.Icon);
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! flareup@2.0.0 build: `parcel build pages/*.js pages/*.css`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the flareup@2.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/steve/.npm/_logs/2021-02-02T16_26_04_786Z-debug.log