Package: Add @wordpress/custom-templated-path-webpack-plugin package

[aduth]

This pull request seeks to add a new package: @wordpress/custom-templated-path-webpack-plugin. This has been extracted from an inline class definition in Gutenberg's webpack.config.js, and updated for Webpack 4+ .

Refer to included README.md for more information.

Testing instructions:

See: WordPress/gutenberg#5687

[codecov]

Codecov Report

Merging #93 into master will decrease coverage by 2.08%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master      #93      +/-   ##
==========================================
- Coverage   73.45%   71.36%   -2.09%     
==========================================
  Files          35       38       +3     
  Lines         437      461      +24     
  Branches       82       86       +4     
==========================================
+ Hits          321      329       +8     
- Misses         98      112      +14     
- Partials       18       20       +2

Impacted Files	Coverage Δ
.../custom-templated-path-webpack-plugin/src/index.js	0% <0%> (ø)
...d-path-webpack-plugin/test/fixtures/entry/index.js	0% <0%> (ø)
...ath-webpack-plugin/test/fixtures/webpack.config.js	88.88% <88.88%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3c62e78...712e599. Read the comment docs.

[ntwb]

This initial version here needs to not be 1.0.0, @gziolo has used "version": "1.0.1-0", in the past which has worked fine though I think we should use 1.0.0-alpha.

This all because Lerna bumps this version upon release, if it were to stay at 1.0.0 then Lerna would only be able to publish a patch 1.0.1, minor 1.1.0, or major 2.0.0 release and a 1.0.0 version would never be published.

[aduth]

Well, that's annoying 😄 Maybe it'd be fine to publish an initial release manually, without Lerna?

[gziolo]

I think it wasn’t expected to be landed 😃

[aduth]

😞

[aduth]

At least it's in a test file.

[gziolo]

I need to add this to jest-console 😎

[gziolo]

By the way, what was the reason you avoided import/export statements? In src subfolder it’s perfectly fine to use all Babel friendly code. Build step generates 2 versions by default.

[aduth]

Because it doesn't transpile to CommonJS-compatible. If using export default, consuming projects need to require via require( '@wordpress/custom-templated-path-webpack-plugin' ).default (note .default).

[gziolo]

Right, that reminds me I sort of did the same for node based packages 😃
The only difference is that I put them in the root folder to skip Babel magic. Both work similar.
I think it isn’t the case for tests though.