Update webpack-config-jaid: 3.3.0 → 3.15.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ webpack-config-jaid (3.3.0 → 3.15.0) · Repo

Release Notes

3.15.0

Changelog

• Added option hashbang (if it is set to a string, its value will be added at the start of the entry script's content)
• Upgraded dependencies

---

Code changes: v3.14.1 … v3.15.0

3.14.1

Changelog

• Fixed handling of option includeMonacoEditor

---

Code changes: v3.14.0 … v3.14.1

3.14.0

Changelog

• Allowed option includeMonacoEditor to be an array
• Upgraded dependencies

---

Code changes: v3.13.0 … v3.14.0

3.13.0

Changelog

• Changed force indicator for style-loader usage, it's now forced when process.env.webpackPort is set, and not in every development environment

---

Code changes: v3.12.0 … v3.13.0

3.11.0

Changelog

• Added option optimizeCss for type webapp (true by default)
• Added option createCssFile for type webapp (true by default)
• Fixed Webpack publicPath options for most cases
• Improved production output file naming
• Set a byte limit of 4000 for url-loader (file-loader will be used if asset size exceeds the threshold)

---

Code changes: v3.10.1 … v3.11.0

3.10.1

Changelog

• Added missing dependency url-loader

---

Code changes: v3.10.0 … v3.10.1

3.10.0

Changelog

• Added more file extensions to url-loader rule

---

Code changes: v3.9.0 … v3.10.0

3.9.0

Changelog

• Added resolve-url-loader

---

Code changes: v3.8.0 … v3.9.0

3.8.0

Changelog

• Removed loader for .postcss files
• Restricted babel-loader scope to PROJECT/src
• Restricted CSS modules scope to PROJECT/src
• Dependency upgrade

---

Code changes: v3.7.0 … v3.8.0

3.7.0

Changelog

• Added option includeMonacoEditor

---

Code changes: v3.6.4 … v3.7.0

Not all release notes shown. View the full release notes

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[Jaid]

Removing depfu integration. Thank you for your service, but I am going to look for alternatives.