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.

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

[Bug] Htmlextra does not support newman v6 #416

Closed
1 task done
arunthiagarajan opened this issue Sep 15, 2023 · 7 comments
Closed
1 task done

[Bug] Htmlextra does not support newman v6 #416

arunthiagarajan opened this issue Sep 15, 2023 · 7 comments
Labels
area: newman-related This issue relates to the Newman project state: triaged This issue has been triaged type: bug Something isn't working

Comments

@arunthiagarajan
Copy link

arunthiagarajan commented Sep 15, 2023 •
edited by DannyDainton
Loading

Is There An Existing Issue

What Are You Seeing

<html>
<body>
<!--StartFragment-->

Container] 2023/09/15 12:28:43 Running command npm install newman-reporter-htmlextra
--
95 | npm ERR! code ERESOLVE
96 | npm ERR! ERESOLVE unable to resolve dependency tree
97 | npm ERR!
98 | npm ERR! While resolving: undefined@undefined
99 | npm ERR! Found: [email protected]
100 | npm ERR! node_modules/newman
101 | npm ERR!   newman@"^6.0.0" from the root project
102 | npm ERR!
103 | npm ERR! Could not resolve dependency:
104 | npm ERR! peer newman@"^5.1.2" from [email protected]
105 | npm ERR! node_modules/newman-reporter-htmlextra
106 | npm ERR!   newman-reporter-htmlextra@"*" from the root project
107 | npm ERR!
108 | npm ERR! Fix the upstream dependency conflict, or retry
109 | npm ERR! this command with --force, or --legacy-peer-deps
110 | npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
111 | npm ERR!
112 | npm ERR! See /root/.npm/eresolve-report.txt for a full report.
113 |  
114 | npm ERR! A complete log of this run can be found in:
115 | npm ERR!     /root/.npm/_logs/2023-09-15T12_28_43_550Z-debug-0.log
116 |  
117 | [Container] 2023/09/15 12:28:43 Command did not exit successfully npm install newman-reporter-htmlextra exit status 1

<!--EndFragment-->
</body>
</html>

Steps To Reproduce The Issue

1.npm install newman
2.npm install newman-reporter-htmlextra

Full Newman Command Or Node Script

1.npm install newman
2.npm install newman-reporter-htmlextra

HTMLEXTRA Version

1.22.11

Newman Version

v6.0.0

Additional Context

No response
@arunthiagarajan arunthiagarajan added state: needs-triage This issue needs to be triaged type: bug Something isn't working labels Sep 15, 2023
@github-actions
Copy link

Hey @arunthiagarajan: 👋 - Thanks for helping to make the reporter better by raising this ticket. I will take a look as soon as I can and get back to you. Cheers, Danny.

@DannyDainton
Copy link
Owner

DannyDainton commented Sep 16, 2023 •
edited
Loading

Hey @arunthiagarajan

Thanks for raising this issue, I kinda suspected that this might happen with this reporter and potentially a few others.

Newman v6 only supports node v16 and above and there might be some incompatibility with the modules in the reporter.

I need to spend some time to understand what I need to change in order to get this working with the new version of Newman.

As you can appreciate, this is a side project and not my main job, I'll get to this as soon as I can but I can't give a specific timeline.

Downgrading to V5 of Newman is the only quick solution right now.

@DannyDainton DannyDainton added area: newman-related This issue relates to the Newman project state: triaged This issue has been triaged and removed state: needs-triage This issue needs to be triaged labels Sep 16, 2023
@DannyDainton DannyDainton changed the title newman-reporter-htmlextra plugin does support latest version of newman v6.0.0 [Bug] Htmlextra does not support newman v6 Sep 16, 2023
@w4dd325
Copy link
Contributor

w4dd325 commented Sep 18, 2023

I just tested this with newman v6 and it works for me. (I also use Node v20)

image

I found I had some residual files from earlier versions, so I would suggest running,

npm uninstall newman -g
npm uninstall newman-reporter-htmlextra -g

and then re-installing both and trying again.

@PiotrLisowski88
Copy link

Hi,
newman-reporter-htmlextra@"1.22.11" works with newman 6.0.0. when using --force only.

Please prepare the fix in order to run npm ci without any conflicts.

While resolving: my-repository
Found: [email protected]
node_modules/newman
dev newman@"^6.0.0" from the root project

Could not resolve dependency:
peer newman@"^5.1.2" from [email protected]
node_modules/newman-reporter-htmlextra
dev newman-reporter-htmlextra@"1.22.11" from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

@w4dd325
Copy link
Contributor

w4dd325 commented Nov 29, 2023

newman-reporter-htmlextra@"1.22.11" works with newman 6.0.0. when using --force only.

Hi @PiotrLisowski88
In the screenshot above I ran newman-reporter-htmlextra 1.22.11 with Newman 6, without using --force.

I found I had some residual files from earlier versions of Newman and had to run the uninstall command (with -g) to ensure it was cleaned before installing Newman 6. (The fact that newman@"^5.1.2" is referenced makes me think this could be the same issue I saw).

I also updated Node to v20 - what version of Node are you running?

@PiotrLisowski88
Copy link

Hi, @w4dd325,
I also don't have a problem with running newman-reporter-htmlextra 1.22.11 with Newman 6. The report is generating and all is fine BUT my issue lies with INSTALING the libraries.

I working on 20.8.1 Node and in my project I have Newman 6.0.0. and when I am trying to install npm install -D newman-reporter-htmlextra@latest without --force it shows me this:
image

That's why after I install with --force which I shouldn't do it - I can't just perform npm ci in my project because there is conflict with reporter and newman version.

I tried deleted node_modules and uninstall -g newman

@scotty6435 scotty6435 mentioned this issue Dec 4, 2023
Merged
@github-actions GitHub Actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area: newman-related This issue relates to the Newman project state: triaged This issue has been triaged type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@DannyDainton @arunthiagarajan @w4dd325 @PiotrLisowski88