You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My name is Moses.
I have been working on a project to build a GitHub Action that utilizes the ts-migrate package to convert JS code to TS. Th action will automate the conversion process and I plan to publish it on the GitHub marketplace.
I have run into an issue where the package is failing to be installed in an Ubuntu Docker image which forms part of the Action despite the package installing fine on my PC using the npm install --save-dev ts-migrate command.
I keep on getting the error message Tracker "idealTree" already exists.
I have tried clearing the npm cache in the Docker image using the npm cache clean --force command and also ensured that I use the same npm and node versions as on my PC but the error keeps persisting.
Is this a bug or if not can you please help me sort the issue out. Here's the link to the project repo in-case you need some context on the issue.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
My name is Moses.
I have been working on a project to build a GitHub Action that utilizes the ts-migrate package to convert JS code to TS. Th action will automate the conversion process and I plan to publish it on the GitHub marketplace.
I have run into an issue where the package is failing to be installed in an Ubuntu Docker image which forms part of the Action despite the package installing fine on my PC using the
npm install --save-dev ts-migrate
command.I keep on getting the error message
Tracker "idealTree" already exists
.I have tried clearing the npm cache in the Docker image using the
npm cache clean --force
command and also ensured that I use the same npm and node versions as on my PC but the error keeps persisting.Is this a bug or if not can you please help me sort the issue out. Here's the link to the project repo in-case you need some context on the issue.
Thanks.
The text was updated successfully, but these errors were encountered: