Missing export should be a compile error

[gaearon]

This is only relevant in master which uses Webpack 2.

If I change src/index.js from

import App from './App';

to

import {App} from './App';

I'm getting:

The screen is blank (because of the runtime error).

Notice how the real problem is at the very bottom (missing export), yet it looks like the first two are the important ones.

The terminal output is also very restrained (because it is a warning):

I wonder what are the reasons for this. I think a missing ES6 export should totally be a compile error because it is so easy to mess it up, and then have weird runtime errors as a result.

I have two questions:

• Why isn’t in an error by default?
• Can we make this an error in CRA setup?

[Timer]

Seems like we need to set strictModuleExceptionHandling to true.
It was added but never documented, and that's why we missed it.

[gaearon]

Rad. Anybody wants to make a PR?

[insin]

The config schema documentation for this says "Handles exceptions in module loading correctly at a performance cost" - should this be switched on in production builds?

[Timer]

Perhaps we can test it on a relatively large application? Would anyone be willing to do this?

[insin]

It looks like this config triggers generation of try/catch wrappers when calling the generated module function at runtime, but doesn't upgrade missing modules to an error at build time.

• Warning generation
• (Presumption) Usage

[Timer]

After further investigation after what @insin, it seems strictModuleExceptionHandling isn't what we want (despite some various sources I found). It looks like we need to add a custom hook to parse the webpack warnings.

Maybe @sokra could give us some more insight?

[mqklin]

+1, doesn't work for me. I've added output: { strictModuleExceptionHandling: true } option in webpack config and import { nonexistentModule } from 'someFile' in a source file, no errors in terminal.

[sokra]

strictModuleExceptionHandling is not related to import. It's about exceptions in modules. There is currently no way to make the warning an error (except with a custom plugin).

[gaearon]

Is there a reason why? I’m just curious what the rationale is.

[sokra]

Some typescript constructs emit incorrect import/exports (related to the loader impl, not sure if it's fixed now). So we used a warning. But I guess it fine to add an option upgrading it to an error.

[Timer]

See issue webpack/webpack#4347 and PR webpack/webpack#4348.

[Timer]

Once webpack/webpack#4348 is merged we will be able to set module.strictExportPresence to true for this behavior.

Is it worth setting strictModuleExceptionHandling to true? From what I understand it's more compliant with spec.

/cc @gaearon

[gaearon]

I'd rather avoid a try catch in init code.

[Timer]

module.strictExportPresence was merged. Waiting for webpack release.

[Timer]

Released in WP 2.3.0.