pico-engine
pico-engine copied to clipboard
Published
20 hours ago •
Picolab
Picolab
Pico engine build has errors
Reported by Paul Wenzel (see log attached).
"Changing strict: true to strict: false in the tsconfig.json files fixes the problems. I am still surprised that it used to be working two months ago."
Don't see how to attach a file, so here it is, in-line:
git clone https://github.com/Picolab/pico-engine.git
Cloning into 'pico-engine'...
remote: Enumerating objects: 28604, done.
remote: Counting objects: 100% (112/112), done.
remote: Compressing objects: 100% (83/83), done.
remote: Total 28604 (delta 60), reused 62 (delta 25), pack-reused 28492
Receiving objects: 100% (28604/28604), 9.65 MiB | 6.62 MiB/s, done.
Resolving deltas: 100% (21331/21331), done.
pwen at PC192-168-2-101 in /Users/pwen/GitRepos/open-source/picoengine2_
ll
total 0
drwxr-xr-x 18 pwen staff 576 Sep 13 17:36 pico-engine
pwen at PC192-168-2-101 in /Users/pwen/GitRepos/open-source/picoengine2_
cd pico-engine/
pwen at PC192-168-2-101 in /Users/pwen/GitRepos/open-source/picoengine2/pico-engine_(master)
npm run setup
> pico-engine@ setup /Users/pwen/GitRepos/open-source/picoengine2/pico-engine
> npm i --no-package-lock && npm run bootstrap
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN @octokit/[email protected] requires a peer of @octokit/core@>=3 but none is installed. You must install peer dependencies yourself.
added 780 packages from 389 contributors and audited 780 packages in 17.901s
43 packages are looking for funding
run `npm fund` for details
found 30 vulnerabilities (18 moderate, 12 high)
run `npm audit fix` to fix them, or `npm audit` for details
> pico-engine@ bootstrap /Users/pwen/GitRepos/open-source/picoengine2/pico-engine
> lerna bootstrap --hoist --no-ci --nohoist=browserify --nohoist=@types/* --nohoist=pico-framework
lerna notice cli v3.22.1
lerna info Bootstrapping 7 packages
lerna WARN EHOIST_PKG_VERSION "krl-compiler" package depends on ava@^2.1.0, which differs from the hoisted ava@^1.4.1.
lerna WARN EHOIST_PKG_VERSION "krl-generator" package depends on ava@^2.2.0, which differs from the hoisted ava@^1.4.1.
lerna WARN EHOIST_PKG_VERSION "krl-parser" package depends on ava@^2.4.0, which differs from the hoisted ava@^1.4.1.
lerna info Installing external dependencies
lerna info hoist Installing hoisted dependencies into root
lerna info hoist Pruning hoisted dependencies
lerna info hoist Finished pruning hoisted dependencies
lerna info hoist Finished bootstrapping root
lerna info Symlinking packages and binaries
lerna info lifecycle [email protected]~prepublish: [email protected]
lerna info lifecycle [email protected]~prepublish: [email protected]
> [email protected] prepublish /Users/pwen/GitRepos/open-source/picoengine2/pico-engine/packages/krl-stdlib
> npm run build
> [email protected] build /Users/pwen/GitRepos/open-source/picoengine2/pico-engine/packages/krl-stdlib
> rm -rf dist && tsc
> [email protected] prepublish /Users/pwen/GitRepos/open-source/picoengine2/pico-engine/packages/krl-parser
> npm run build
> [email protected] build /Users/pwen/GitRepos/open-source/picoengine2/pico-engine/packages/krl-parser
> npm run build:ts -s && npm run build:spec -s
src/index.ts:12:14 - error TS2571: Object is of type 'unknown'.
12 if (e && e.setupWhere) {
~
src/index.ts:13:7 - error TS2571: Object is of type 'unknown'.
13 e.setupWhere(src, opts.filename || "");
~
test/expressions.ts:21:22 - error TS2571: Object is of type 'unknown'.
21 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/expressions.ts:21:40 - error TS2571: Object is of type 'unknown'.
21 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/expressions.ts:21:57 - error TS2571: Object is of type 'unknown'.
21 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/postludeStatements.ts:13:22 - error TS2571: Object is of type 'unknown'.
13 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/postludeStatements.ts:13:40 - error TS2571: Object is of type 'unknown'.
13 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/postludeStatements.ts:13:57 - error TS2571: Object is of type 'unknown'.
13 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:13:22 - error TS2571: Object is of type 'unknown'.
13 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:13:40 - error TS2571: Object is of type 'unknown'.
13 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:13:57 - error TS2571: Object is of type 'unknown'.
13 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:88:24 - error TS2571: Object is of type 'unknown'.
88 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:88:42 - error TS2571: Object is of type 'unknown'.
88 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:88:59 - error TS2571: Object is of type 'unknown'.
88 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:139:24 - error TS2571: Object is of type 'unknown'.
139 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:139:42 - error TS2571: Object is of type 'unknown'.
139 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
test/ruleset.ts:139:59 - error TS2571: Object is of type 'unknown'.
139 return `${err}|${err.token.type}|${err.token.src}|${err.token.loc.start}`;
~~~
Found 17 errors.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] build: `npm run build:ts -s && npm run build:spec -s`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/pwen/.npm/_logs/2021-09-13T15_38_12_215Z-debug.log
lerna info lifecycle [email protected]~prepublish: Failed to exec prepublish script
lerna ERR! lifecycle "prepublish" errored in "krl-parser", exiting 2
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! pico-engine@ bootstrap: `lerna bootstrap --hoist --no-ci --nohoist=browserify --nohoist=@types/* --nohoist=pico-framework`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the pico-engine@ bootstrap script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/pwen/.npm/_logs/2021-09-13T15_38_12_267Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! pico-engine@ setup: `npm i --no-package-lock && npm run bootstrap`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the pico-engine@ setup script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/pwen/.npm/_logs/2021-09-13T15_38_12_309Z-debug.log
Error Code 2
@farskipper suggested this answer, "#571 is probably b/c typescript got an update where it's being more strict so we just need to adjust the code so it's properly checked"