liferay-npm-bundler fails if no .npmbundlerrc file is found

[izaera]

A way to fix this would be running liferay-npm-bundler-preset-standard by default if no .npmbundlerrc file is found.

[jbalsas]

Do you mean running liferay-npm-bundler-preset-standard?

[izaera]

Yes. I copy pasted the wrong name. I have edited my first comment.

[izaera]

Oops, I have fixed this with #39, but it assumes an empty .npmbundlerrc instead of sensible defaults, like liferay-npm-bundler-preset-standard.

Shall we change the behavior of #39 in favor of using liferay-npm-bundler-preset-standard or leave it like that?

What do you think @jbalsas?

[jbalsas]

Let's leave it like is for now and see what people expect from using it without a config.

[izaera]

After looking at it in more detail, we will finally set liferay-npm-bundler-preset-standard as the default preset because it follows the more usual build lifecycle.

[izaera]

Oops! This is far more difficult than I thought. Babel doesn't do it either.

The technical problem is that if the bundler assumes a default preset, it has to include the preset internally because the project (to which the bundler is being applied) won't have it. That could be done, but it wouldn't leave control to the user about the version of the preset to use.

Then, we could let users override the preset version by adding a .npmbundlerrc file, but it would make the plugins resolution more complex and could lead to inconsistencies, so I find it safer not to assume a default preset.