samclayton / coriolis Goto Github PK

TODO claims it's inaccurate w/ eng boosters

ENV NODE_OPTIONS=--openssl-legacy-provider in the Dockerfile will work around this, but that prevents VSCode from attaching to the container.

`> [email protected] start

node devServer.js
ℹ ｢wds｣: Project is running at http://localhost:3300/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /app
ℹ ｢wds｣: 404s will fallback to /index.html
Listening at localhost:3300
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (/app/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/app/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/app/node_modules/webpack/lib/NormalModule.js:471:10)
at /app/node_modules/webpack/lib/NormalModule.js:503:5
at /app/node_modules/webpack/lib/NormalModule.js:358:12
at /app/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/app/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at iterateNormalLoaders (/app/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
at /app/node_modules/loader-runner/lib/LoaderRunner.js:236:3
at runSyncOrAsync (/app/node_modules/loader-runner/lib/LoaderRunner.js:130:11)
at iterateNormalLoaders (/app/node_modules/loader-runner/lib/LoaderRunner.js:232:2)
at Array. (/app/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
at Storage.finished (/app/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
at /app/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
node:internal/crypto/hash:71
this[kHandle] = new _Hash(algorithm, xofLen);
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (/app/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/app/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/app/node_modules/webpack/lib/NormalModule.js:471:10)
at /app/node_modules/webpack/lib/NormalModule.js:503:5
at /app/node_modules/webpack/lib/NormalModule.js:358:12
at /app/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/app/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at Array. (/app/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
at Storage.finished (/app/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
at /app/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
at /app/node_modules/graceful-fs/graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Node.js v18.14.0`

Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://fb.me/prop-types-docs

see also https://github.com/reactjs/react-codemod#react-proptypes-to-prop-types

$ npm install
npm ERR! code 2
npm ERR! git dep preparation failed
npm ERR! command /usr/local/Cellar/node/15.12.0/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/Users/samworks/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit
npm ERR! > [email protected] prepublish
npm ERR! > npm run build
npm ERR!
npm ERR!
npm ERR! > [email protected] build
npm ERR! > npm run build_light && node coriolis_mapper.js
npm ERR!
npm ERR!
npm ERR! > [email protected] build_light
npm ERR! > tsc
npm ERR!
npm ERR! src/data/blueprints.ts(14,29): error TS2307: Cannot find module './blueprints.json' or its corresponding type declarations.
npm ERR! src/data/blueprints.ts(15,32): error TS2307: Cannot find module './experimentals.json' or its corresponding type declarations.
npm ERR! src/data/index.ts(15,31): error TS2307: Cannot find module './module_cache.json' or its corresponding type declarations.
npm ERR! src/data/items.ts(15,26): error TS2307: Cannot find module './modules.json' or its corresponding type declarations.
npm ERR! src/data/ships.ts(11,24): error TS2307: Cannot find module './ships.json' or its corresponding type declarations.
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm ERR! npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm ERR! npm WARN deprecated [email protected]: this library is no longer supported
npm ERR! npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm ERR! npm WARN deprecated [email protected]: use String.prototype.padStart()
npm ERR! npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm ERR! npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! npm WARN deprecated @types/[email protected]: This is a stub types definition. handlebars provides its own type definitions, so you do not need this installed.
npm ERR! npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm ERR! npm WARN deprecated [email protected]: Support has ended for 9.x series. Upgrade to @latest
npm ERR! npm WARN using --force Recommended protections disabled.
npm ERR! npm WARN using --force Recommended protections disabled.

xdLocalStoragePostMessageApi.min.js appears to exist to post build to orbis.zone, a now-defunct service.

What's more, it's unmaintainable minified js that exists in an iframe.
Essentially, just revert this commit, which appears to be the only commit referencing it. At least this is an atomic operation.

https://github.com/SamClayton/coriolis/blob/develop/src/app/i18n/en.json
and potentially elsewhere

Triage & update the most dire.

/app # npm install npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated [email protected]: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s). npm WARN deprecated [email protected]: this library is no longer supported npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-node-resolve. npm WARN deprecated [email protected]: use String.prototype.padStart() npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin. npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated [email protected]: 3.x is no longer supported npm WARN deprecated @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information. npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

Coriolis.jsx:349 Storage may be cleared by the UA under storage pressure.

https://developer.mozilla.org/en-US/docs/Web/API/StorageManager/persist

see /src/app/stores/Persist.js

--legacy-peer-deps

Is this data going into a black hole that no dev ever looks at? If so, just kill it, at minimum on dev server build.
Also, where is this GA data going?
All of this sounds like an annoying performance hit during dev.

[3:35 AM] Reiver: On the subject of tools, what would be really neat is knowing not so much what materials you need (I mean, you've got it already, it's pretty handy), but which engineers you've signed up for - a way to combine down the minimum number of visits needed, as it were. Knowing you can get your engines and FSD at Farseer, then the Dweller is doing your lasers while Broo is doing ... etc
Sure, if you're engineering everything to level 5, you're going to be doing a lot of flying, but there can definitely be conviniences to pausing and looking at "Wait, do I really need that engineer?"
[3:36 AM] alterNERDtive (bindED): that’s way out of scope, and also spansh is working on that
alterNERDtive (bindED): afai understand his plans you’ll feed his “engineering router” the engineers you have and a build (e.g. exported from coriolis) and it gives you a route to go engineer the stuff
10:33 AM] Fett_Li / felixlinker (coriolis): oh. well, since I don't want to deal with engineers anyways, I guess it doesn't matter 😄
[10:33 AM] alterNERDtive (bindED): well, coriolis needs to at least put blueprints and grades in the builds =p
[10:33 AM] Fett_Li / felixlinker (coriolis): yes!

From React v16.0 Blog Post:

... With minor exceptions, if your app runs in 15.6 without any warnings, it should work in 16.
For deprecations listed in packaging below, codemods are provided to automatically transform your deprecated code. See the 15.5.0 blog post for more information, or browse the codemods in the react-codemod project.

The app currently targets 15.5.4. There are codemods for this transition.

Updating may confer a 3-10x performance increase, as well as incorporating bug & security fixes, and may address npm install issues.

The only way to tell apart 2 similar truncated names currently is by order of ships above graphs.

"engine": "node >= 4.8.1",

Check for usages of shouldComponentUpdate()

react-addons-perf no longer works at all in React 16. It’s likely that we’ll release a new version of this tool in the future. In the meantime, you can use your browser’s performance tools to profile React components.

Module abbrevs in src/app/shipyard/Constants.js may or may not need change.

Ref EDCD#650

number-editor is relying on react-clickdrag, which hasn't been updated in 3+ years. react-container-dimensions is of a similar age.

The former seems to just allow click-dragging numbers in e.g. engineering specs, which strikes me as a not particularly important feature, and one which may be done by another package. The latter will need more investigation, though its README includes a list of similar projects, one of which might be actively maintained.

ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! Found: [email protected] npm ERR! node_modules/react npm ERR! react@"^16.14.0" from the root project npm ERR! peer react@"^0.14.0 || ^15.0.0 || 16.x" from [email protected] npm ERR! node_modules/react-container-dimensions npm ERR! dev react-container-dimensions@"^1.4.1" from the root project npm ERR! 8 more (react-dom, react-extras, react-fuzzy, react-ga, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"0.14.x || ^15.0.0-rc" from [email protected] npm ERR! node_modules/react-number-editor/node_modules/react-clickdrag npm ERR! react-clickdrag@"^3.0.2" from [email protected] npm ERR! node_modules/react-number-editor npm ERR! react-number-editor@"^4.0.3" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Appears to be a Webpack plugin that pairs with iframe.html to facilitate LocalStorage access. Unclear why. Minified js is unmaintainable, so best to replace it. At minimum, can a readable version be compiled by Webpack as part of build proc?

Perhaps only for review/staging app builds on Heroku/Github? How might the pre-production instances more closely match production?

https://devcenter.heroku.com/articles/node-best-practices#hook-things-up
https://help.heroku.com/P1AVPANS/why-is-my-node-js-app-crashing-with-an-r10-error