
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
@lokalise/frontend-http-client
Advanced tools
Opinionated HTTP client for the frontend.
Note that it is a ESM-only package.
import wretch from 'wretch'
import { z } from 'zod'
const client = wretch('http://localhost:8000')
const queryParamsSchema = z.object({
param1: z.string(),
param2: z.number(),
})
const requestBodySchema = z.object({
requestCode: z.number(),
})
const responseBodySchema = z.object({
success: z.boolean(),
})
const responseBody = await sendPost(client, {
path: '/',
body: { requestCode: 100 },
queryParams: { param1: 'test', param2: 123 },
queryParamsSchema,
requestBodySchema,
responseBodySchema,
})
SDK methods has a parameter (isEmptyResponseExpected
) to specify if 204 response should be treated as an error or not. By default it is treated as
valid except on sendGet
method where it is treated as an error. Usage example:
const response = await sendGet(client, {
path: '/',
isEmptyResponseExpected: true,
})
if 204
responses are expected, the library will return null, if not, it will throw an error.
SDK methods has a parameter (isNonJSONResponseExpected
) to specify if non json responses should be treated as an error
or not. By default it is treated as valid except on sendGet
method where it is treated as an error. Usage example:
const response = await sendGet(client, {
path: '/',
isNonJSONResponseExpected: true,
})
if non-JSON responses are expected, the library will return null, if not, it will throw an error.
frontend-http-client
supports using API contracts, created with @lokalise/universal-ts-utils/api-contracts/apiContracts
in order to make fully type-safe HTTP requests.
Usage example:
import { somePostRouteDefinition, someGetRouteDefinition } from 'some-service-api-contracts'
import { sendByPayloadRoute } from '@lokalise/frontend-http-client'
import wretch from 'wretch'
const client = wretch(BASE_URL)
const responseBody1 = await sendByPayloadRoute(client, somePostRouteDefinition, {
pathParams: {
userId: 1,
},
body: {
isActive: true,
},
})
const responseBody2 = await sendByGetRoute(client, someGetRouteDefinition, {
pathParams: {
userId: 1,
},
queryParams: {
id: 'testId',
},
})
This library is brought to you by a joint effort of Lokalise engineers:
FAQs
Opinionated HTTP client for the frontend
The npm package @lokalise/frontend-http-client receives a total of 1,992 weekly downloads. As such, @lokalise/frontend-http-client popularity was classified as popular.
We found that @lokalise/frontend-http-client demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 17 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.