-
Notifications
You must be signed in to change notification settings - Fork 86
Feature/jss 105 refactor auth services from elysia to express #892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Ansonhkg
wants to merge
81
commits into
feature/jss-93-refactor-bun-pnpm
Choose a base branch
from
feature/jss-105-refactor-auth-services-from-elysia-to-express
base: feature/jss-93-refactor-bun-pnpm
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Feature/jss 105 refactor auth services from elysia to express #892
Ansonhkg
wants to merge
81
commits into
feature/jss-93-refactor-bun-pnpm
from
feature/jss-105-refactor-auth-services-from-elysia-to-express
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sistency across all packages
…will be using the logger package instead
```ts await client.authService.mintWithAuth({ authData, authServiceBaseUrl, scopes, apiKey: 'YOUR_API_KEY', }); ``` ```ts await WebAuthnAuthenticator.registerAndMintPKP({ authServiceBaseUrl, scopes, apiKey: 'YOUR_API_KEY', }); ``` Upcoming PR to use .overrides authBaseUrl and API key instead.
- fixed env should be service specific - added html packages back to lit-login-server - renamed lit-*-service to lit-*-server - return express instance for devs to customise - pinned @ts-oss/env-cors version This commit has also been tested locally using the E2E test dApp
…bstract-provider' or its corresponding type declarations.
…Cannot find module '@ethersproject/contracts' or its corresponding type declarations.` error from `packages/access-control-conditions/src/lib/humanizer.ts:1:26`
…y` and update main entry point to index.ts
…rsion 21.2.1, removing deprecated settings and adjusting package versions for compatibility
…ority of them came from `createContractManager` which supplies incompatible client shapes (or mixing public/wallet inference) made Client generics collide. Explicit PublicClient annotation triggered heavy generic expansion and account mismatches. Letting TS infer the type from createPublicClient resolves this. - removed capacity credits as we have remove this concept for Naga - Using `LitResourceAbilityRequestSchema` inferred type instead of legacy `CapacityDelegationRequest` (Types to be removed) - Login server Node's CJS resolving dir name - types on JobStatus - declare the `auth-services` package as types node - replaced @ts-expect-error in error.ts to @ts-ignore - fixed the type from Ajv - Introduced StrictAuthData instead of inline type - bindAccount helper in the createChainManagerFactory to fix signature mismatch - updated targets from ES2020 to ES2022
…xecutable via node eg. `NODE_OPTIONS=--no-deprecation node ./dist/apps/lit-login-server/main.cjs`
…rver with updated Dockerfiles and README instructions; include .dockerignore for build optimization
Closed
…/LIT-Protocol/js-sdk into feature/jss-105-refactor-auth-services-from-elysia-to-express
… run tests by path
…d remove obsolete scripts
…ker release workflow
…rver to use multi-platform support and streamline dependency installation
…servers in README
…as CommonJS again so bundlers stop loading the build artifacts in ESM mode and hitting exports runtime errors - Point the few packages whose main/types fields were still referencing the old ./dist paths at the real build outputs instead, so consumers resolve the CJS entry on first try instead of falling through to the broken ESM path
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WHAT
Migrated away from using Elysia (Optimised for Bun) to Express.
Commands to start the services
Usage
Docker build
Note: The publish pipeline is not setup yet, but these commands basically what we need to publish it to GHCR. This also allow us to provide one-click deploy on Railway or any other platforms.