Closed crutchcorn closed 5 years ago
Thanks for PR @crutchcorn I'll check that today and get back with the feedback
Two questions I had (that might be potentially out-of-scope for this PR:
1) Should the project build both files with one command? It does not do so currently
2) Is there a need/want for pushing dist
to the repo. There is a postinstall
hook for npm
and yarn
that could handle the build when the user npm install
/yarn install
s. I understand there seems to be wanted bower
support, but I know their site defers to yarn
for the front-end
@crutchcorn about 2nd part of your question
Is there a need/want for pushing dist to the repo
I've added /dist to a repo to be able to access it directly in browser environment - https://github.com/shershen08/vue-masonry#usage-directly-in-the-browser
about
Should the project build both files with one command? It does not do so currently
true, there was no need in this, since it's just a plugin library - I am not developing/building it on daily basis
@shershen08 unkpg
uses npm
to get the files. You could still build dist
for the npm
package, but then not host the build on GitHub. Minor argument that doesn't matter too much either way, just a thought 🤷♀️
I get not needing to build it regularly. I'm just very lazy for my own libraries and am easily forgetful about the build steps myself 😅
@shershen08 was there more feedback for this PR or do you think it should be ready to go?
This merge requests updates to babel@8, webpack@4, eslint@5