Skip to content
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

add npm run actions, remove github: prefix, ios-deploy optionalDependency #1081

Merged
merged 1 commit into from
Sep 30, 2021
Merged

add npm run actions, remove github: prefix, ios-deploy optionalDependency #1081

merged 1 commit into from
Sep 30, 2021

Conversation

daniellacosse
Copy link
Contributor

@daniellacosse daniellacosse commented Sep 27, 2021

@google-cla google-cla bot added the cla: yes label Sep 27, 2021
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
src/electron/build_action.sh Outdated Show resolved Hide resolved
@daniellacosse
Copy link
Contributor Author

daniellacosse commented Sep 29, 2021

ah @fortuna this is the crux of the version mismatch:

So when I accidentally ran yarn in this project, electron-builder complained - but then I remembered we were supposed to use npm and I started fresh and it worked. Kept it at v12, However in the CI it explicitly asks for v14. I have two ways to proceed:

  1. upgrade outline-server to v14 and see what happens
  2. provide an .nvmrc and instructions for switching versions across the different projects via nvm use

I'm gonna try #1 first - I guess I'll just run a bunch of the actions and see if anything comes up? From what I've seen so far our testing strategy seems uneven.

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: undefined,
npm WARN EBADENGINE   required: { node: '^12', npm: '^6' },
npm WARN EBADENGINE   current: { node: 'v12.22.6', npm: '7.24.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'app-builder-lib@22.11.7',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.6', npm: '7.24.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'electron-builder@22.11.7',
npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.6', npm: '7.24.1' }
npm WARN EBADENGINE }

README.md Outdated Show resolved Hide resolved
package.json Outdated
@@ -41,6 +42,7 @@
"electron-promise-ipc": "^2.2.4",
"electron-updater": "^4.1.2",
"fs-extra": "^7.0.0",
"ios-deploy": "^1.11.4",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Revert. This is a transitive dependency, I believe.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't work for me, if i revert it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What version of NPM should I be using? Wonder if this is causing it, and the issue here

Screen.Recording.2021-09-29.at.4.00.28.PM.mov

Copy link
Contributor Author

@daniellacosse daniellacosse Sep 29, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NPM V7 seems to have fixed the github: thing i was seeing, but it still won't build unless i explicitly add ios-deploy - either globally or this way

Copy link
Contributor Author

@daniellacosse daniellacosse Sep 30, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

found it - this happens when you have xcode open or your iphone connected to your mac apache/cordova-ios#420

Copy link
Contributor Author

@daniellacosse daniellacosse Sep 30, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using optionalDependencies seems to be the solution - linux ignores it on failure, but it's installed locally on mac in case the dev has their phone plugged in

@daniellacosse daniellacosse changed the title add yarn actions, and fix ShadowsocksConfig macro, webpack bin add npm run actions, remove github: prefix, ios-deploy (?) Sep 29, 2021
@daniellacosse daniellacosse changed the title add npm run actions, remove github: prefix, ios-deploy (?) add npm run actions, remove github: prefix, ios-deploy optionalDependency Sep 30, 2021
@daniellacosse daniellacosse merged commit d42fc02 into Jigsaw-Code:master Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants