-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old depreciated Global Expo CLI checks in Doctor command changed #2618
Conversation
rm expo and added warning for depr
yarn test
yarn run v1.22.21
$ TS_JEST_DISABLE_VER_CHECKER=true jest
PASS src/tools/packager.test.ts
PASS src/tools/demo.test.ts
PASS test/vanilla/ignite-help.test.ts (10.631 s)
PASS test/vanilla/ignite-remove-demo.test.ts (11.145 s)
PASS test/vanilla/ignite-generate.test.ts (37.078 s)
FAIL test/vanilla/ignite-new.test.ts (121.722 s)
● ignite new › ignite new Foo --debug --packager=bun --yes › should be able to use `generate` command and have pass output pass bun run test, bun run lint, and bun run compile scripts
Command failed: cd /private/var/folders/32/m_87zp_n3218j0y94jfsywdw0000gn/T/ignite-e1873a30238044ba33c0e3a2e7e33f9b/Foo && bun run test && cd /Users/dax/Code/contribs/ignite
$ jest
FAIL app/models/ModTest.test.ts
● Test suite failed to run
TypeError: Cannot redefine property: performance
at Object.<anonymous> (node_modules/react-native/jest/setup.js:409:20)
FAIL app/models/Episode.test.ts
● Test suite failed to run
TypeError: Cannot redefine property: performance
at Object.<anonymous> (node_modules/react-native/jest/setup.js:409:20)
FAIL app/services/api/apiProblem.test.ts
● Test suite failed to run
TypeError: Cannot redefine property: performance
at Object.<anonymous> (node_modules/react-native/jest/setup.js:409:20)
FAIL app/utils/storage/storage.test.ts
● Test suite failed to run
TypeError: Cannot redefine property: performance
at Object.<anonymous> (node_modules/react-native/jest/setup.js:409:20)
FAIL test/i18n.test.ts
● Test suite failed to run
TypeError: Cannot redefine property: performance
at Object.<anonymous> (node_modules/react-native/jest/setup.js:409:20)
Test Suites: 5 failed, 5 total
Tests: 0 total
Snapshots: 0 total
Time: 3 s
Ran all test suites.
error: script "test" exited with code 1 (SIGHUP)
Test Suites: 1 failed, 5 passed, 6 total
Tests: 1 failed, 33 passed, 34 total
Snapshots: 31 passed, 31 total
Time: 122.154 s
Ran all test suites.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. Getting the above errors this is the only blocker but I don't immediately see how my changes broke these tests. |
Will do later in the week. Thanks for insight. I'm sick in the hospital right now. |
Hey sorry I thought would be a quick fix so I actually did all this on the master of my fork. So I instead removed a dead else statement I missed before and it ran again. I even reinstalled bun as I had it before when I ran it? Do I need to be doing something different? |
Looks like you could get it to pass CI by running |
Ohh I have to force the linter to run idk why I thought it did that itself. Sorry sick brain. |
file created when reinstalling bun didnt see it slip in
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @Dax911 ! First off thanks for the contribution and hope you are feeling better.
I love the idea of the expo-cli warning, that's a great addition!
However, I think we could still restore the managed/bare expo workflow to the info table, as this was related to the project directory the command is being run in and not part of the global install checks.
Let me know your thoughts and again, be well!
Yea, I actually did this after chatting w @jamonholmgren about the Expo CLI being returned as I wasn't even sure what tool it was referring to anymore. I totally could have gotten over excited in my sick and slashing things mindset. I will take second look I think you are right. I am seeing that you are right and that it is unrelated to that specific check... I am curious tho what purpose this Edit: Also it only shows up if the expo CLI is installed and provides value only if ur using a deprecated tool? |
OH, it all just clicked yes your right thank you! Will make that change. |
adds warning to doctor when dep cli tool is installed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Dax911 thanks for the updates! a few code consistency comments and some color to highlight the deprecation warning and I think this will be good to go!
Thanks again
src/commands/doctor.ts
Outdated
@@ -110,6 +125,7 @@ module.exports = { | |||
...pnpmPackages, | |||
bunInfo, | |||
expoInfo, | |||
...(depExpoCLIInfo ? [depExpoCLIInfo] : []), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...(depExpoCLIInfo ? [depExpoCLIInfo] : []), | |
depExpoCliInfo, |
I believe table knows what to do with a null value here, so we can just simplify this up!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't believe you are correct here. And I was right I tested it with your change and the result was
ignite-cli doctor
System
platform darwin
arch arm64
cpu 8 cores Apple M2
directory ignite /Users/dax/Code/contribs/ignite
JavaScript (and globally-installed packages)
/Users/dax/Code/contribs/ignite/node_modules/gluegun/node_modules/cli-table3/src/layout-manager.js:143
return rows.map(function (row) {
^
TypeError: Cannot convert undefined or null to object
at Function.keys (<anonymous>)
at /Users/dax/Code/contribs/ignite/node_modules/gluegun/node_modules/cli-table3/src/layout-manager.js:145:26
at Table.map (<anonymous>)
at generateCells (/Users/dax/Code/contribs/ignite/node_modules/gluegun/node_modules/cli-table3/src/layout-manager.js:143:17)
at Object.makeTableLayout (/Users/dax/Code/contribs/ignite/node_modules/gluegun/node_modules/cli-table3/src/layout-manager.js:161:20)
at Table.toString (/Users/dax/Code/contribs/ignite/node_modules/gluegun/node_modules/cli-table3/src/table.js:23:29)
at table (/Users/dax/Code/contribs/ignite/node_modules/gluegun/src/toolbox/print-tools.ts:136:17)
at Command.<anonymous> (/Users/dax/Code/contribs/ignite/src/commands/doctor.ts:118:5)
at step (/Users/dax/Code/contribs/ignite/src/commands/doctor.ts:33:23)
at Object.throw (/Users/dax/Code/contribs/ignite/src/commands/doctor.ts:14:53)
I can leave it as is, create another PR to fit the table handling a null case, since its from Gluegun I can check the docs to see if does have info on gracefully handling null otherwise we can revert please advise.
I will take care of it. Sorry I'm weird I like to always capitalize CLI and short stuff like that. Totally a me thing didn't realize I was breaking that pattern, thanks for the call out! |
All good, you're helping us! And it's appreciated :) |
case errors fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey sorry, I might have made a poor suggestion with the yellow color but I think you need the column3 helper still!
forgot to push
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made fixes and ran tests
made this change i just forgot to push it. It should be there. |
## [9.6.1](v9.6.0...v9.6.1) (2024-02-21) ### Bug Fixes * **boilerplate:** jest.config.js remove jsdom test env for better RNTL support out of box ([#2632](#2632) by [@frankcalise](https://github.com/frankcalise)) ([22c7afc](22c7afc)) * **boilerplate:** remove `yarn prebuild` script in favor of clean ([#2635](#2635) by [@frankcalise](https://github.com/frankcalise)) ([f669a32](f669a32)) * **boilerplate:** web hmr fixes ([#2646](#2646) by [@frankcalise](https://github.com/frankcalise)) ([45aabb2](45aabb2)) * **cli:** Global Expo CLI checks in Doctor command ([#2618](#2618) by @Dax911) ([d0b2b2d](d0b2b2d)) * **components:** switch animation slide on web ([#2642](#2642) by [@frankcalise](https://github.com/frankcalise)) ([c0dcc6d](c0dcc6d))
🎉 This PR is included in version 9.6.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Please verify the following:
yarn test
jest tests pass with new tests, if relevantREADME.md
has been updated with your changes, if relevantDescribe your PR
I cleaned up the old expo global cli tool install check for the
doctor
command. I added in a warning dialogue for developers who still have it installed.