Closed nabdelgadir closed 5 years ago
CI is failing but it says No identified problem No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.
I don't believe it's related.
The only change in question is whether we want to introduce
package-lock.json
.
@raymondfeng @bajtos, what's your thought on that? Thanks.
We are intentionally NOT USING package-lock files in LB3 repositories. I am open to discuss a switch to package locking, but not in this PR please.
Please remove package-lock.json
file from the patch.
@bajtos @dhmlau I didn't mean to add the package-lock.json
s (to this one or other related PRs). They were being generated when I did npm i
and I didn't notice them but I'll take them out of the PRs they're in. Thanks!
Related issues
Checklist