Skip to content

Conversation

@patrickarlt
Copy link
Contributor

@patrickarlt patrickarlt commented Nov 24, 2025

Now that we are free from Karma and Jasmine (yay @dixonyant!) I've updated the dependencies for TypeScript, TypeDoc, ESLint and Rollup. This fixes problems with peer dependencies and means we can go back to normal npm install instead of npm install --legacy-peer-deps.

this also makes a bunch of other changes including:

  • Resolves a bunch of random linting errors that came up as a result of updating the linting libraries and TypeDoc.
  • Add and configure changesets to manage releases.

@patrickarlt patrickarlt marked this pull request as draft November 24, 2025 16:31
@patrickarlt

This comment was marked as outdated.

@dixonyant dixonyant changed the title Update depenedencies Update dependencies Nov 24, 2025
@patrickarlt patrickarlt marked this pull request as ready for review December 29, 2025 19:28
Copy link
Contributor

@dixonyant dixonyant left a comment

Choose a reason for hiding this comment

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

LGTM!

IFeatureSet
} from "@esri/arcgis-rest-request";

export interface IFeatureSetWithGeoJson extends IFeatureSet {
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm interested as to what this is doing as I may have run into an overlapping type issue with the query library response that also extends this IFeatureSet, returning both geojson and arcgis under the features prop

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The routing methods work a little different and return a geoJson property next to a features property. I think what you are looking for is function overloads I cooked up something in #821 (comment) that I think we should look at for v5 since I think that changing the types would be a breaking change.

Copy link
Contributor

Choose a reason for hiding this comment

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

That was a fantastic read and nice rabbit hole to jump down. Gives a lot of context

export interface IGetApiKeyOptions extends Omit<IRequestOptions, "params"> {
/**
* {@linkcode IAuthenticationManager} authentication.
* {@linkcode @esri/arcgis-rest-request!IAuthenticationManager} authentication.
Copy link
Contributor

Choose a reason for hiding this comment

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

wow was this all it needed? :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yup. It was buried in the doc on declaration references

Copy link
Contributor

@noahmulfinger noahmulfinger left a comment

Choose a reason for hiding this comment

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

Typos and a few questions

*
* A {@linkcode ArcGISAccessDeniedError} error will be thrown if the user denies the request on the authorization screen.
*
* @browserOnly
Copy link
Contributor

@noahmulfinger noahmulfinger Dec 30, 2025

Choose a reason for hiding this comment

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

  1. So was support dropped for @browserOnly and @nodeOnly tags?\
  2. How will these typedoc changes affect our typedoc processing on the developer website?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We never actually supported these on the developer website. We just moved this info into the comment.

RELEASE.md Outdated
As of v4, the ArcGIS REST JS packages are released automatically via Semantic Release.
In Late 2025 ArcGIS REST JS now uses [changesets](https://github.com/changesets/changesets) to manage releases. This happens automatically using the default [changeset action](https://github.com/changesets/action) in the [release workflow](./.github/workflows/release.yml). When changes are merge to `main` changesets will automatically creates a PR that when merged will trigges a new release of all packages.

As a part of these changes all versions of ArcGIS REST JS packages are how synced to the highest minor version accross all packages. All packages will now maintain the same version number for ease of reference.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it the case that "all packages will now maintain the same version number"? Isn't that dependent on the changeset keyword used (patch or minor)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes but they will all be bumped to the same version (patch/minor/major) together. Keeping everything on the same version will make things like the support lifecycles easier

patrickarlt and others added 2 commits December 30, 2025 12:49
@github-actions
Copy link

Code Coverage

Package Line Rate Branch Rate Complexity Health
arcgis-rest-basemap-sessions.src 100% 100% 0
arcgis-rest-basemap-sessions.src.utils 100% 100% 0
arcgis-rest-demographics.src 100% 100% 0
arcgis-rest-developer-credentials.src 100% 100% 0
arcgis-rest-developer-credentials.src.shared 100% 100% 0
arcgis-rest-elevation.src 100% 100% 0
arcgis-rest-feature-service.src 100% 100% 0
arcgis-rest-geocoding.src 100% 100% 0
arcgis-rest-places.src 100% 100% 0
arcgis-rest-portal.src.groups 100% 100% 0
arcgis-rest-portal.src.items 100% 100% 0
arcgis-rest-portal.src.orgs 100% 100% 0
arcgis-rest-portal.src.services 100% 100% 0
arcgis-rest-portal.src.sharing 100% 100% 0
arcgis-rest-portal.src.users 100% 100% 0
arcgis-rest-portal.src.util 100% 100% 0
arcgis-rest-request.src 100% 100% 0
arcgis-rest-request.src.types 100% 100% 0
arcgis-rest-request.src.utils 100% 100% 0
arcgis-rest-routing.src 100% 100% 0
Summary 100% (2182 / 2182) 100% (1209 / 1209) 0

Minimum allowed line rate is 100%

@patrickarlt patrickarlt merged commit 93db38b into main Dec 30, 2025
3 checks passed
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