another contribution from me. hopefully, this one is more foolproof
code standards have been difficult for me to follow given that there's no linters or code formatters configured, but i did the best i can. also, it doesn't look like the .editorconfig is actually being consumed given that i see variations of indentation throughout the files?
additionally, it would be useful if the src itself was bundled in the npm artifact, as you can consume that directly in other webpack projects. for contributors, you can alias or symlink the dependency to wherever the forked repo exists on disk to allow for seamless manual verification. it also just allows for a common entrypoint when checking out from git while waiting for the upstream to accept the changes
another contribution from me. hopefully, this one is more foolproof
code standards have been difficult for me to follow given that there's no linters or code formatters configured, but i did the best i can. also, it doesn't look like the
.editorconfigis actually being consumed given that i see variations of indentation throughout the files?additionally, it would be useful if the
srcitself was bundled in the npm artifact, as you can consume that directly in other webpack projects. for contributors, you can alias or symlink the dependency to wherever the forked repo exists on disk to allow for seamless manual verification. it also just allows for a common entrypoint when checking out from git while waiting for the upstream to accept the changes