eneajaho / ngx-libs Goto Github PK

View Code? Open in Web Editor NEW

73.0 5.0 30.0 3.14 MB

Angular Libraries Support lists community libs support for each Angular version

Home Page: https://ngx-libs.com/

License: MIT License

HTML 1.39% TypeScript 97.91% SCSS 0.51% JavaScript 0.19%

angular libraries ng support update

ngx-libs's Introduction

Angular Libraries Support ⛱️

While ng updating Angular projects, it is important to know if a library has added support for the new Angular version. This project is supposed to solve this problem by providing a list of libraries and their support for different Angular versions.

How to use

Filter the list by Angular version or library name. Click on the links to get to the library's repository, release page or npm page.

How to contribute

Take the issue

If you want to take one issue, feel free to use .take in the issue comment

Automatic

To add a new library, run the following command:

npm run add-lib

Please leave feedback so we can improve the generator

To edit an existing library, please refer to Manual

Manual

If you want to add a library, please create a pull request with the following changes:

Add the library to the libs.data.ts file

How to run locally

Clone the repository
Run npm install
Run npm start

License

MIT

ngx-libs's People

Contributors

Stargazers

Watchers

ngx-libs's Issues

add bot to check libs automatically if they are on latest version

ng2-dragula

ngx-tour-core

https://www.npmjs.com/package/@fullcalendar/angular

[feature] add a generator to help add new libraries easier

We should create a nx/plugin (if not already) with a generator that accepts inputs to populate lib.data.ts for new libraries

ngx-moment

feat: take the issue with .take

I saw this issue, many people work on the same issue at the same time, with this feature I want to implement an action in GitHub that is triggered from '.take' in the comment issue, and automatically their issue will be assigned to him.

ngx-img-cropper

ngx-ui-tour-core

add most popular libs based on npm install

add link to PR that updates the library (for libs in progress)

save filtering state in url so it's exportable

add SSR and hydration + SEO for reachability

Add LICENSE file

Currently, the readme just mentions MIT with no link.

add compare mode to check if we can update

add compare mode with possibility to add libs and show what has support and which ones not

Cli tool that would scan package.json and verify against this dataset.

Suggestion from twitter

attach domain ngx-libs.com

add filter for has support / doesn't have support

to better check which libs have support and not

https://www.npmjs.com/package/ngx-filesaver

https://www.npmjs.com/package/@coreui/angular

create blog post to explain how it works, how it solves and how to easily contribute

show all contributors below the table using github api

https://www.npmjs.com/package/ngx-papaparse

[feature] 🚀 Mix with https://update.angular.io/

I propose that we mix it with the content of https://update.angular.io/.

We can use Puppeteer of https://pptr.dev/ to get the right data.

But I don't know if it is legal to get the data with by scrapping.

add button to create PR to the library to migrate it to the latest version

Add ngx-spinner

@flowjs/ngx-flow

https://www.npmjs.com/package/ngx-pipes

ngx-progressbar

ngx-color-picker

https://www.npmjs.com/package/@azure/msal-angular

https://www.npmjs.com/package/ng-mocks

Fix `rx-angular/state` GitHub URL

Fix rx-angular/state GitHub URL. Should be https://github.com/rx-angular/rx-angular/tree/main/libs/state

Contributions count ?

Should we show contributions count?

https://www.npmjs.com/package/ngx-spinner

https://github.com/hakimio/ngx-ui-tour

ngx-tour-ngx-bootstrap

@ngrx/component-store

https://www.npmjs.com/package/angular-split

ngx-clipboard

fix style for UI alignment

[feature] support range versions

Currently, we only support lib version <-> angular version as a 1-1 relationship. In reality, many packages support multiple Angular versions while staying on the same major version. We should come up with a way to support range version. For example:

package-a
    v3.0.0 supports Angular 16+ (signal)
    v2.0.0 supports Angular 14 -> Angular 15 (standalone)
    v1.0.0 supports Angular 9 -> Angular 13 (Ivy)

For example a script that checks what libraries need to be updated when upgrading a project to some Angular version (Could be part of this repo actually)

Project example

"@angular/core": "^13.0.0"
"ngx-toast": "^14.0.0",
"ngx-old-legacy": "^13.0.0"

npx ngx-libs migrate 16 --check (check depedencies' versions)

*  You need to upgrade ngx-toast to version 17.0.0
*  ngx-old-legacy is not compatible with Angular 16

npx ngx-libs migrate 15 --apply (apply the updates (if compatible))

npx ngx-libs migrate --supported (search for common supported Angular version)

* You can peacefully migrate to Angular 15
* The latest Angular 16 version is not yet supported by some packages:
  - ngx-old-legacy

[Feature] site automation

Hi, love the idea!

IMO the whole process should be automated.

UI should fetch packages from a backend+db api
the backend should:
- save a list of packages to check
- for each package, save in db all the versions that the we "saw" already
- each package version should be tagged with the supported angular versions.
  ie:

name: "ngx-foo",
version: "17.0.3",
angular: [16,17]

for each package, check every X for new release
- check if the new package has peer dependencies for angular, if so - add to db with the corresponding tag
- if no, try to install inside sandbox, if passed add the support
- for better support we can add some isVerefied flag or isBroken or any kind of flags that the community can help to maintain in order to avoid false positive by the process.

thoughts?