Skip to content

Releases: internxt/drive-web

v1.0.764

14 May 06:37
a318290

Choose a tag to compare

Description

The purpose of this PR is to capture and log information about file or folder uploads using the Network Information API. How it works:

Each successful upload generates a log containing the upload context and the connection status at that moment. This log includes:

  • file or folder name,
  • size in bytes
  • connection type,
  • effective type
  • estimated download speed,
  • maximum speed
  • latency
  • whether data-saving mode is enabled.

A new module has been created in src/app/network/networkInformation.ts to centralize this functionality. Here are two functions: getNetworkInformation(), which returns the 6 API fields, or null if the browser does not support it, and logNetworkInfoForUpload(context), which combines the upload context with the network information and outputs it to the console.

The functionality has been integrated into three existing upload flows: UploadManager.ts, UploadFolderManager.ts, and uploadFolderThunk.ts.

The log is only output when the upload completes successfully. If the browser does not support the Network Information API, as is the case with Safari or Firefox, the upload proceeds normally and no additional information is logged.

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

To test this feature, a preview deployment was used at https://0559a382.drive-web.pages.dev/ and verified across Chrome, Safari, and Firefox.

Chrome — Network Information API is supported. After a successful file or folder upload, the following log appears in the console:

[Upload] Network information: { fileName: "...", fileSize: ..., effectiveType: "4g", downlink: 9.8, rtt: 0, saveData: false, type: undefined, downlinkMax: undefined }
type and downlinkMax are undefined as expected — Chrome does not implement those two fields on desktop.

Safari — Network Information API is not supported. Uploads complete successfully with no network log and no errors in the console.

Firefox — Network Information API is intentionally disabled by Mozilla for privacy reasons. Uploads complete successfully with no network log and no errors in the console.

Additional Notes

v1.0.763

12 May 07:53
34175d2

Choose a tag to compare

Description

In this PR, we resolved an issue related to the plans we offer that aren’t displayed on the website and are used for other purposes. The point is that these plans have their own IDs and could appear at checkout, so they must be accounted for. Previously, we assumed that if a plan wasn’t one of the three we have on website, it would be the free plan and we used the 1GB path, this is no longer the case. To address this:

  • We have modified the JSONs so that it is no longer the 1GB plan but the default one, we dynamically pass the size in bytes to this JSON
  • We’ve also updated the checkoutProductCard so it can recognize when a plan has specific features (Array.isArray—this is done because if that’s not the case, it literally returns the path) or should use the default features. The approach for the title is the same

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

We have verified that the standard plans continue to display as expected and that these special plans are now being displayed. Examples:

  • planId=price_1RjEJPFAOdcgaBMQifUoiJgL
  • planId=price_1RBxrfFAOdcgaBMQxbEQlLsI

Additional Notes

v1.0.762

12 May 06:54
d104f76

Choose a tag to compare

Bumps @babel/plugin-transform-modules-systemjs from 7.27.1 to 7.29.4.

Release notes

Sourced from @​babel/plugin-transform-modules-systemjs's releases.

v7.29.4 (2026-05-05)

🐛 Bug Fix

  • babel-plugin-transform-modules-systemjs
    • #17974 [7.x backport]fix(systemjs): improve module string name support (@​JLHwung)

Committers: 1

v7.29.3 (2026-04-30)

👓 Spec Compliance

🐛 Bug Fix

  • babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators
    • #17931 fix(decorators): replace super within all removed static elements (@​JLHwung)
  • babel-register
  • babel-compat-data, babel-plugin-bugfix-safari-rest-destructuring-rhs-array, babel-preset-env

💅 Polish

📝 Documentation

🏃‍♀️ Performance

  • babel-helper-import-to-platform-api, babel-plugin-proposal-import-wasm-source, babel-plugin-transform-json-modules

Committers: 4

v7.29.2 (2026-03-16)

👓 Spec Compliance

  • babel-parser

🐛 Bug Fix

  • babel-helpers, babel-plugin-transform-async-generator-functions, babel-preset-env, babel-runtime-corejs3
  • babel-preset-env

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​babel/plugin-transform-modules-systemjs since your current version.


v1.0.761

11 May 14:09
8f1eb9c

Choose a tag to compare

Description

Adding a column for trash view called "Original location" where we display the parent folder name to give the user more context.

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

Additional Notes

v1.0.760

11 May 12:17
74eec3c

Choose a tag to compare

Description

This PR aims to fix an issue where coupon-only sales were failing to attribute on Impact.

Changes included:

  • Added a fallback uuidV4 for anonymousId: Ensures that conversions without a prior affiliate tracking cookie (impactAnonymousId) provide a valid tracking identifier to our analytics integration, preventing silent payload drops.

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

Additional Notes

v1.0.759

11 May 10:26
98ebfed

Choose a tag to compare

Description

Reverts #1918 due to mobile login

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

v1.0.758

11 May 10:06
72f798a

Choose a tag to compare

Description

This PR removes deprecated old token

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

unit tests

v1.0.757

11 May 07:23
24e4931

Choose a tag to compare

Description

Cleaning up payments-related code as B2B plans will no longer be supported in the integrated checkout.

This PR removes:

  • Unused functions
  • Unused components
  • Unused B2B-related styles
  • B2B subscription handling logic

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

Additional Notes

v1.0.756

07 May 10:18
271a4f2

Choose a tag to compare

Description

The behavior of the backup keys dialog reminder has been updated. Now, it will be displayed every 30 days, starting the user is authenticated. It will not be displayed after the authentication.

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

Additional Notes

v1.0.755

07 May 07:10
3dc1c74

Choose a tag to compare

Description

After login or registration, a modal will appear reminding the user to download their backup key. The behavior is:

  • If the user has never seen the dialog, it opens automatically.
  • The user can download the backup key at any time using the download button.
  • Clicking "Remind me later" dismisses the dialog and will not show it again for 14 days or he is authenticated again.
  • Once the user downloads the key and clicks "I've saved my key", the dialog will never be shown again.
  • If the user logs in with a different account, the dialog will appear again for that account (state is stored per user).
  • The dialog will not appear again after logout and login (with the same account) if the user already acknowledged it.
  • While the dialog is open, promotional banners should be hidden.

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

Additional Notes