fix: yarn.lock is missing when compiling the package as a dependency #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #23
Like
package-lock.json
,yarn.lock
will be ignore if not present to the root folder:One key detail about package-lock.json is that it cannot be published, and it will be ignored if found in any place other than the toplevel package.
https://docs.npmjs.com/cli/v6/configuring-npm/package-lock-json
So just make it optional from the Makefile.