Update webpack.config.js

[louy]

Load resolve option from custom webpack config file.

I don't always like adding the ".jsx" extension to my "require" calls.

[louy]

I can also add resolve.alias option, which would solve #44.

[arunoda]

I think it's safe to allow the whole resolve API. Not just extensions and resolve.
Adding .js and node_modules is a clever idea. I like it.

[arunoda]

@louy with the above comment, I think alias thing will work too.

[arunoda]

Additionally, we need to copy any other field in the customConfig except for the following map:

{
  "context": true,
  "entry": true,
  "output": true,
  "module": true,
  "resolve": true,
  "resolveLoader": true,
  "externals": true,
  "target": true,
  "devtool": true,
  "devServer": true,
  "node": true,
  "amd": true,
  "loader": true,
  "recordsPath": true,
  "recordsInputPath": true,
  "recordsOutputPath": true,
  "plugins": true
}

This helps us to support postCss and similar.
See: #43 (comment)

[achebatko]

+1 for resolve.alias

[crooy]

for me an overridable resolve field will solve the same jsx problem for me

[BowlingX]

I would also include preLoaders in module to support eslint and others.

[arunoda]

Thanks to @eloytoro's PR #64 now we can use resolve and other custom webpack configurations.
Try version: 1.5.0.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit bedbb65. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build -c production --parallel=3

---

Sent with 💌 from NxCloud.