Closed jeffmaury closed 1 year ago
Not sure where that comes from:
as we have the license specified.
Check if ..\..\..\..\..\package.json
is not pointing to a stray package.json file. As when I made one in a lower path it started to use/parse this one:
PS> yarn --
yarn install v1.22.19
warning ..\..\package.json: No license field
warning package-lock.json found.
and when removed.
PS> yarn --
yarn install v1.22.19
warning package-lock.json found.
This is not a build issue, but rather yarn
finding something way way way down in the structure.
yarn build
reports: