npmpackage.info

Gathering detailed insights and metrics for @nativescript/firebase-messaging-core

@nativescript/firebase-messaging-core

@nativescript plugins to help with your developments.

3.3.2

191

Apache-2.0

TypeScript

123,701 2.9

Installations

npm install @nativescript/firebase-messaging-core

Pull Requests

Open

9

Total

293

Closed

21

Merged

263

Issues

Open

149

Total

310

Closed

161

Releases

Unable to fetch releases

Developer

NativeScript

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

Yes

Node Version

22.5.1

NPM Version

10.8.2 Statistics

191 Stars

653 Commits

109 Forks

26 Watching

37 Branches

70 Contributors

Updated on 28 Nov 2024

Languages

TypeScript (78.69%)

Swift (6.51%)

Objective-C (4.45%)

Java (3.69%)

Kotlin (2.87%)

HTML (2.09%)

JavaScript (1.22%)

CSS (0.24%)

Shell (0.11%)

Ruby (0.07%)

SCSS (0.07%)

Total Downloads

Cumulative downloads

Total Downloads

123,701

Last day

20.7%

338

Compared to previous day

Last week

-8.2%

1,609

Compared to previous week

Last month

25.1%

6,979

Compared to previous month

Last year

46.9%

69,843

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

Versions

How to use?

This workspace manages the suite of plugins listed above.

Prerequisites

Node 18+ is recommended
yarn v1 is required

In general, when in doubt with what to do, just npm start.

1npm run setup
2npm start
3
4// Ensure all plugins build properly first
5> type "build-all" (and hit ENTER)

If you don't build all the plugins, you will at least need to build localize to run the demos because it contains hooks that need to be built first.

If building only localize, type: npm start > localize (this will narrow down menu to @nativescript.localize.build) and then hit 'enter'. You can now run the demo apps.

In general, when in doubt with what to do, just npm start.

How to add a new package to workspace?

1npm run add

At the prompt, enter the name of the new package.

This adds a plugin harness in packages with the necessary boilerplate to just start developing
Updates all demo app flavors to support demoing the new package
Adds shared code in tools/demo where you can write demo code once and share across all demo flavors
Updates build tooling to support the new package
Updates the npm start interactive display
Updates the README here to list the new package

How to add Angular compatibility to a package

1npm run add-angular

At the prompt, enter the name of the package to add an angular folder to it with the necessary boilerplate to provide Angular support to the package.

How to focus on just 1 package to develop in isolation

1npm start

Choose the focus commands for the package you wish to focus on and hit enter.
All the demo app's will be updated to isolate that 1 package and for supported IDE's (currently VS Code), the source code will also become isolated in the workspace.

Note: good to always clean the demo you plan to run after focusing. (You can clean any demo from npm start as well)

How to publish packages?

1npm run publish-packages

You will be prompted for the package names to publish. Leaving blank and hitting enter will publish them all.
You will then be prompted for the version to use. Leaving blank will auto bump the patch version (it also handles prerelease types like alpha, beta, rc, etc. - It even auto tags the corresponding prelease type on npm).
You will then be given a brief sanity check 🧠😊

Made with ❤️

No vulnerabilities found.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

7

Maintained

Determines if the project is "actively maintained".

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

0

Security-Policy

Determines if the project has published a security policy.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

Score

2.9

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More