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

EPIC-2335: Cordova hook to strip the x86_64 architecture from the iOS framework #138

Open
wants to merge 1 commit into
base: qa
Choose a base branch
from

Conversation

eddyfrank
Copy link
Member

Example for the automation of step https://docs.scanbot.io/barcode-scanner-sdk/cordova/barcode-scanner/#ios
(based on customer issues and questions)

@eddyfrank
Copy link
Member Author

@marcosaia1812 BTW, why don't we switch to "lockfileVersion": 2 in the package-lock.json ?

@marcosaia1812
Copy link
Contributor

marcosaia1812 commented Sep 15, 2022

@marcosaia1812 BTW, why don't we switch to "lockfileVersion": 2 in the package-lock.json ?

@eddyfrank

For the lock file lockfileVersion we know this:

Version 1: used by npm v5 and v6.
Version 2: used by npm v7; backwards compatible
Version 3: used by npm v7, not backwards compatible

Cordova's framework depends on node-sass ^4.0.0

We cannot update to NPM v7 because of this:

NodeJS | Supported node-sass version
Node 17 | 7.0+
Node 16 | 6.0+
Node 15 | 5.0+, <7.0
Node 14 | 4.14+
Node 13 | 4.13+, <5.0
Node 12 | 4.12+
Node 11 | 4.10+, <5.0
Node 10 | 4.9+, <6.0
Node 8 | 4.5.3+, <5.0
Node <8 | <5.0 | <57

This means we can only go up to Node 14, which comes with NPM v6.14 and lockfileVersion = 1

This is my setup now:

~ %  $ npm --version
6.14.11
~ %  $ node --version
v14.15.5

Source:
https://docs.npmjs.com/cli/v7/configuring-npm/package-lock-json#lockfileversion
https://www.npmjs.com/package/node-sass
https://nodejs.org/en/download/releases/

@marcosaia1812 marcosaia1812 changed the title Cordova hook to strip the x86_64 architecture from the iOS framework EPIC-2335: Cordova hook to strip the x86_64 architecture from the iOS framework Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

3 participants