lula / ngx-soap

Simple SOAP client for Angular
MIT License
66 stars 60 forks source link

Angular 13 support #125

Open efgiese opened 2 years ago

efgiese commented 2 years ago

Hi,

is there a plan to support Angular 13? It would be very nice...

sopadespachar commented 2 years ago

Hi,

I copied to local and upgrade to Angular 14. Works fine until now. Please, valid my fork.

JorgeMoV commented 2 years ago

Hi,

I have tried your fork, @sopadespachar , and after executing: npm install --save buffer concat-stream core-js crypto-js events lodash sax stream uuid npm install sopadespachar/ngx-soap --save

I get the following error when compile after add the import on "app.module.ts": Cannot find module 'ngx-soap' or its corresponding type declarations.

Import: import { NgxSoapModule } from 'ngx-soap';

The package is not available despite being installed correctly inside the node_modules folder and despite appearing in package.json

Could you help me? I need this package to work with angular 14. Thanks in advance.

sopadespachar commented 2 years ago

Hi @JorgeMoV

I doesn't commit a release.

In my local machine, I generate a new lib:

npm run build:lib

Enter in cd .\dist\ngx-soap\

And create a package: npm pack

After this I install my package: npm install FOLDER\ngx-soap-0.1X.0.tgz –force

JorgeMoV commented 2 years ago

Thank you for your nice help. I'm trying to follow those steps, but it's the first time I've done something like this and I'm having problems.

I have cloned your fork like this: git clone https://github.com/sopadespachar/ngx-soap.git

I then went into the ngx-soap folder and ran npm install.

Then I have executed the first command that you indicate: npm run build:lib

and the following error appears: Error: Could not find the '@angular-devkit/build-ng-packagr:build' builder's node package.

I have tried to install that package by doing: npm install @angular-devkit/build-ng-packagr

And I get the following error:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: ngx-soap@0.14.0
npm ERR! Found: ng-packagr@14.2.2
npm ERR! node_modules/ng-packagr
npm ERR!   dev ng-packagr@"^14.2.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer ng-packagr@"^10.0.0" from @angular-devkit/build-ng-packagr@0.1002.0
npm ERR! node_modules/@angular-devkit/build-ng-packagr
npm ERR!   @angular-devkit/build-ng-packagr@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Can you guide me please, because I'm trying to solve the error in all possible ways and I can't. Thank you very much for your help.

sopadespachar commented 2 years ago

It's my first time too.

Try to add the --force to resolve this issue.

JorgeMoV commented 2 years ago

Yes, that was the solution, use -force.

Now, after following your steps, the module is imported into the project and I hope it works correctly. At the moment it seems so.

Thank you very much for your help sir, it was very important for me to get the module working.

elineopsommer commented 1 year ago

@sopadespachar is it possible to create a new release since this one seems to be dead? :)

seyfer commented 11 months ago

this project was a wrapper around https://github.com/vpulim/node-soap just use node-soap directly if you need to convert XML response to JSON use https://github.com/NaturalIntelligence/fast-xml-parser

seyfer commented 10 months ago

Hi @JorgeMoV

I doesn't commit a release.

In my local machine, I generate a new lib:

npm run build:lib

Enter in cd .\dist\ngx-soap\

And create a package: npm pack

After this I install my package: npm install FOLDER\ngx-soap-0.1X.0.tgz –force

If you have CI/CD such as GitHub actions, does it mean you will need to build lib in CI process on each npm install?

like:

  1. clone my project, run npm i
  2. clone ngx-soap
  3. cd to ngx-soap, npm i and build lib
  4. cd back to project, install ngx-soap from it's location

it means it is not possible to make these changes permanent, right?

seyfer commented 10 months ago

Hey guys, I have updated this package to v16, creating a version and a release on npm from v10 until v16.

I did it only because I needed it on my current project, where it was outdated and a blocker.

NPM: https://www.npmjs.com/package/ngx-soap-next GitHub: https://github.com/seyfer/ngx-soap

feel free to use and contribute, I am going to maintain it for some time.

WilliamAndreu commented 5 months ago

Hi guys, i update that library for angular 17 here ---> https://www.npmjs.com/package/ngx-hybrid-soap