[bugfix] webpack-cli init loader's test regex

[CroMarmot]

What kind of change does this PR introduce?
bugfix

Did you add tests for your changes?
no

If relevant, did you update the documentation?
no

Summary

Fixed the regular expression of loader's test field in webpack.config.js generated by webpack-cli init

Does this PR introduce a breaking change?
no

Other information

the regex should be \.jsx?$ or \.(js|jsx)$, the original string should be "/\\.(js|jsx)$/" instead of /.(js|jsx)$/

the same with "/.(ts|tsx)?$/" -> "/\\.(ts|tsx)$/"

/.(ts|tsx)?$/.test("anystring") === true
/.(ts|tsx)$/.test("anystringts") === true
/\.(ts|tsx)$/.test("anystring.ts") === true

[jsf-clabot]

All committers have signed the CLA.

[ghost]

There were the following issues with this Pull Request

• Commit: 4d6d022
  • ✖ message may not be empty
  • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.

---

🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[ematipico]

Hi! Thank you for your contribution! Could you sign the license agreement please?

[rkaw92]

Leaving this here for posterity: if you, like me, are having problems where require('./style.css') from a TypeScript file seems to do absolutely nothing where it should invoke style-loader, it may be caused by this.

Apparently, Webpack configs generated by a buggy version of this init tool where both ts-loader and style-loader are active may cause ts-loader to override loading of .css files (due to the RegExp issue described above), and cause styles to not appear.