Introducing Rules Migration Tooling

Hi @rueben.tiow,

Yes, I understand that, unfortunately that does not address the question. I am referring to getting type definitions available in local IDEs, for example by publishing them under @types/ on NPM or elsewhere, for example as a part of the existing node-auth0 package.

There were already other requests for this:

Currently we have some local scripts to munch through the vendor.js file from Auth0 Actions online editor page and generate the following files for each type (trigger) which we can then use within our code repository:

  • CredentialsExchangeV2.d.ts
  • LoginPostIdentifierV1.d.ts
  • PasswordResetPostChallengeV1.d.ts
  • PostChangePasswordV2.d.ts
  • PostLoginV3.d.ts
  • PostUserRegistrationV2.d.ts
  • PreUserRegistrationV2.d.ts
  • SendPhoneMessageV2.d.ts

I appreciate that the online Actions editor experience is great with new features like the Rules migration suggestions, although changes alike do not have any impact when used outside of that site, e.g. in IntelliJ or VSCode. Growing support things like Auth0 provider for Terraform is enabling teams to work on Actions more effectively and securely. For example, we would like to limit global access to Auth0 Dashboard and manage changes with source control and CI, however that is not really possible if the development experience outside of the Actions editor is poor without type definitions, type checking, code completion, etc.

1 Like