Hi,

You’re welcome to start a Discussion thread about this on GitHub if you’d like 
to find community support for the issue, but officially we no longer support 
versions prior to 4.1.x, and I believe Applitools no longer supports that 
package (they changed a bunch of licenses and privatized things if I recall 
correctly).

I’d recommend upgrading to 4.1.3 or 5.0.0.

Thanks!

-e-

Evan Rusackas
Preset | preset.io
Apache Superset PMC
On Jul 18, 2025 at 4:57 AM -0700, Tharindu Akalanka 
<tharindu.akalanka...@gmail.com>, wrote:
> Dear Team,
>
> I am getting this error when building the superset 2.1.1.
> Since this tgz has been removed from the repository, Is there a way to find
> this tgz file or could you send the tgz file.
>
> https://registry.npmjs.org/@applitools/test-server/-/test-server-1.1.16.tgz
>
> https://raw.githubusercontent.com/apache/superset/refs/tags/2.1.1/superset-frontend/package-lock.json
>
> Log
>
> 224.8 npm notice
> 224.8 npm notice New major version of npm available! 8.19.4 -> 11.4.2
> 224.8 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v11.4.2
> >
> 224.8 npm notice Run `npm install -g npm@11.4.2` to update!
> 224.8 npm notice
> 224.8 npm ERR! code E404
> 224.8 npm ERR! 404 Not Found - GET
> https://registry.npmjs.org/@applitools/test-server/-/test-server-1.1.16.tgz -
> Not found
> 224.8 npm ERR! 404
> 224.8 npm ERR! 404 '@applitools/test-server@
> https://registry.npmjs.org/@applitools/test-server/-/test-server-1.1.16.tgz'
> is not in this registry.
> 224.8 npm ERR! 404
> 224.8 npm ERR! 404 Note that you can also install from a
> 224.8 npm ERR! 404 tarball, folder, http url, or git url.
> 224.8
> 224.8 npm ERR! A complete log of this run can be found in:
> 224.8 npm ERR! /root/.npm/_logs/2025-07-17T12_27_12_746Z-debug-0.log
> ------
> Dockerfile:17
> --------------------
> 15 |
> 16 | COPY superset-frontend/package*.json ./
> 17 | >>> RUN npm ci
> 18 |
> 19 | COPY ./superset-frontend .
> --------------------
> ERROR: failed to solve: process "/bin/sh -c npm ci" did not complete
> successfully: exit code: 1
>
> Thank you
> Tharindu Akalanka

Reply via email to