No source maps in development mode

[ozyx]

Summary

Recently, we updated app.js to conditionally use webpack.dev.js if NODE_ENV === 'development'. However, this is never set, causing OpenMCT to use production/test webpack configs. This is breaking sourcemaps in development mode.

Fix is to also use webpack.dev.js if NODE_ENV is not set.

Expected vs Current Behavior

OpenMCT should produce sourcemaps in development mode, but it's not.

Steps to Reproduce

1. Ensure NODE_ENV is not set: unset NODE_ENV
2. npm install
3. npm start
4. Examine the source and notice there are no sourcemaps

Environment

• Open MCT Version: release/2.0.5
• Deployment Type: local
• OS: any
• Browser: any

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information

[ozyx]

Testing Instructions

1. Follow steps to reproduce
2. See that source maps are generated

[jvigliotta]

Verified Fixed - Testathon: 8/11

Source maps showing when NODE_ENV is unset, or set to 'development'.