Thanks to visit codestin.com
Credit goes to github.com

Skip to content

NativeScript Dependencies issues #10192

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.

Sign up for GitHub

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

Jump to bottom
Open
3 tasks done
KunaalMangal opened this issue Jan 31, 2023 · 3 comments
Open
3 tasks done

NativeScript Dependencies issues #10192

KunaalMangal opened this issue Jan 31, 2023 · 3 comments
Labels
bug-pending-triage Reported bug, pending triage to confirm.

Comments

@KunaalMangal
Copy link
Contributor

Issue Description

Hello !

My name is KUNAAL MANGAL, I am from INDIA and I am a hybrid mobile application developer. I currently working in an organization in which I am working on project last from 1yr that is base on NativeScript 6 Angular. Recently I migrate that project NativeScript 6 to NativeScript 8. In the process of Migration of NativeScript 6 to NativeScript 8 I faced lot of challenges, that took my 30-40days and i found following issue with some plugins that i want to share with everyone :-

  1. Update the android api level numbe in types android file 17 to 33( @NativeScript\types-android\lib\android.d.ts
  • /// ).
  1. some plugins is not compaitable with webpack 5
  2. some plugin is still use compile in gradle file instead of implementation for dependency.
  3. some plugin absolutly not working anymore for Nativescript 8
  4. google-services.json file is not automatically linked in android platform folder from App_Resources.

Reproduction

No response

Relevant log output (if applicable)

No response

Environment

No response

Please accept these terms
@KunaalMangal KunaalMangal added the bug-pending-triage Reported bug, pending triage to confirm. label Jan 31, 2023
@vallemar
Copy link
Contributor

vallemar commented Feb 1, 2023

Welcome @KunaalMangal ! what is your problem? It seems that your errors are in the plugins, right?

@KunaalMangal
Copy link
Contributor Author

Hello
@vallemar ,
yes I facing problems in plugins but also in the #NativeScript repository. In Nativescript update the android reference file path for accessing the latest version of android apis :-
Change the reference path file in NativeScript 8 @nativescript/types-android/lib/android.d.ts from android-17.d.ts to android-33.d.ts .

image

@arLevi
Copy link

arLevi commented May 7, 2025 •
edited
Loading

I just run ns update and now I have:

$ tns build android

Support for Node.js 16.14.0 is not verified. NativeScript CLI might not install or run properly.
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@ngtools/[email protected]',
npm WARN EBADENGINE   required: {
npm WARN EBADENGINE     node: '^12.14.1 || >=14.0.0',
npm WARN EBADENGINE     npm: '^6.11.0 || ^7.5.6',
npm WARN EBADENGINE     yarn: '>= 1.13.0'
npm WARN EBADENGINE   },
npm WARN EBADENGINE   current: { node: 'v16.14.0', npm: '8.7.0' }
npm WARN EBADENGINE }
...
webpack 5.99.8 compiled with 1440 errors and 1 warning in 24617 ms
Webpack compilation complete.

1440 errors i'm really lost ... I even git clone my project again, just run tns build android tons of issues...

It was better I think if the project wouldn't be depended on a machine's global npm or node version ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug-pending-triage Reported bug, pending triage to confirm.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@arLevi @vallemar @KunaalMangal