Skip to content

Upgrade node#16

Closed
RezaAkhtar wants to merge 7 commits intoalteryx:mainfrom
RezaAkhtar:upgrade-node
Closed

Upgrade node#16
RezaAkhtar wants to merge 7 commits intoalteryx:mainfrom
RezaAkhtar:upgrade-node

Conversation

@RezaAkhtar
Copy link
Collaborator

No description provided.

@RezaAkhtar RezaAkhtar requested a review from Cmancuso July 14, 2025 18:00
@@ -0,0 +1 @@
v20.19.3
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like the latest of v20 is v20.19.4. It was just released yday (7/15) but might be good to be on this version since it looks like it was a security release

"jest": "^29.7.0",
"jest-cli": "^29.7.0",
"jsdom-global": "^3.0.2",
"react": "^18.3.1",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our gen-ai-designer-tools repo has React at "react": "^16.13.1", and I vaguely recall that React 18 introduces significant changes. This might not be a production issue since it's a dev dependency but the version mismatch might cause dev issues if react-comms is using any React 18 features. Do you foresee any issues?

Here are 3 options that I think we can do:
We could leave this at "react": "^16.13.1" and create later tickets to upgrade both this and gen-ai-designer-tools, have both react 16 || 18 versions that the package can work with, or upgrade to 18 here and address potential dev issues as they come up in gen-ai-designer-tools

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My plan is to upgrade gen-ai-designer-tools to 18, I already have a branch with those changes locally

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be a ts file? Since you've converted the other files

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually only converted one file to a typescript test file, I think we can come back later and change this if we want to - would be a larger refactor

/* eslint-disable no-underscore-dangle */
import React, { useContext } from 'react';
import { render, screen, act } from '@testing-library/react';
// import '@testing-library/jest-dom';
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete?

SetConfiguration: jest.fn(),
GetConfiguration: jest.fn()
GetConfiguration: jest.fn(),
Callbacks: {}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Callbacks should be inside window.Alteryx, not inside the Gui obj. This is what Im using for reference. Also, do the other properties need to be included here? Not sure how what the logic is to determine what gets included or not

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kept getting an error about not having callbacks in Gui, I think possible Callbacks is a field in both

@@ -0,0 +1,202 @@
/* eslint-disable no-underscore-dangle */
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do these tests run in pipeline? or they are just executed manually?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just manually, but I'm going to push up a change so they run in the pipeline

@floorrinse
Copy link
Collaborator

Should probably add to the changelog

@@ -0,0 +1 @@
registry=https://artifactory.alteryx.com/artifactory/api/npm/npm/ No newline at end of file
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove

@RezaAkhtar RezaAkhtar closed this Jul 23, 2025
@RezaAkhtar
Copy link
Collaborator Author

Moving to gitlab

@RezaAkhtar RezaAkhtar deleted the upgrade-node branch July 23, 2025 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants