FM / request

/home/techb158/balavpn.abdallabala.com/node_modules/next/dist/server/request/

/home/techb158/balavpn.abdallabala.com/node_modules/next/dist/server/request

Name	Size	Mode	Actions
connection.d.ts	254	0666	edit dl rm
connection.js	7130	0666	edit dl rm
connection.js.map	8414	0666	edit dl rm
cookies.d.ts	1777	0666	edit dl rm
cookies.js	20619	0666	edit dl rm
cookies.js.map	31400	0666	edit dl rm
draft-mode.d.ts	1925	0666	edit dl rm
draft-mode.js	13865	0666	edit dl rm
draft-mode.js.map	20966	0666	edit dl rm
fallback-params.d.ts	179	0666	edit dl rm
fallback-params.js	1340	0666	edit dl rm
fallback-params.js.map	2129	0666	edit dl rm
headers.d.ts	2347	0666	edit dl rm
headers.js	17752	0666	edit dl rm
headers.js.map	26775	0666	edit dl rm
params.d.ts	2313	0666	edit dl rm
params.js	27221	0666	edit dl rm
params.js.map	39330	0666	edit dl rm
pathname.d.ts	200	0666	edit dl rm
pathname.js	4383	0666	edit dl rm
pathname.js.map	6179	0666	edit dl rm
root-params.d.ts	188	0666	edit dl rm
root-params.js	14372	0666	edit dl rm
root-params.js.map	18482	0666	edit dl rm
search-params.d.ts	2474	0666	edit dl rm
search-params.js	33032	0666	edit dl rm
search-params.js.map	47459	0666	edit dl rm
utils.d.ts	487	0666	edit dl rm
utils.js	3166	0666	edit dl rm
utils.js.map	3169	0666	edit dl rm

Edit: /home/techb158/balavpn.abdallabala.com/node_modules/next/dist/server/request/headers.d.ts (2347B)

import { type ReadonlyHeaders } from '../web/spec-extension/adapters/headers';
/**
 * In this version of Next.js `headers()` returns a Promise however you can still reference the properties of the underlying Headers instance
 * synchronously to facilitate migration. The `UnsafeUnwrappedHeaders` type is added to your code by a codemod that attempts to automatically
 * updates callsites to reflect the new Promise return type. There are some cases where `headers()` cannot be automatically converted, namely
 * when it is used inside a synchronous function and we can't be sure the function can be made async automatically. In these cases we add an
 * explicit type case to `UnsafeUnwrappedHeaders` to enable typescript to allow for the synchronous usage only where it is actually necessary.
 *
 * You should should update these callsites to either be async functions where the `headers()` value can be awaited or you should call `headers()`
 * from outside and await the return value before passing it into this function.
 *
 * You can find instances that require manual migration by searching for `UnsafeUnwrappedHeaders` in your codebase or by search for a comment that
 * starts with `@next-codemod-error`.
 *
 * In a future version of Next.js `headers()` will only return a Promise and you will not be able to access the underlying Headers instance
 * without awaiting the return value first. When this change happens the type `UnsafeUnwrappedHeaders` will be updated to reflect that is it no longer
 * usable.
 *
 * This type is marked deprecated to help identify it as target for refactoring away.
 *
 * @deprecated
 */
export type UnsafeUnwrappedHeaders = ReadonlyHeaders;
/**
 * This function allows you to read the HTTP incoming request headers in
 * [Server Components](https://nextjs.org/docs/app/building-your-application/rendering/server-components),
 * [Server Actions](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations),
 * [Route Handlers](https://nextjs.org/docs/app/building-your-application/routing/route-handlers) and
 * [Middleware](https://nextjs.org/docs/app/building-your-application/routing/middleware).
 *
 * Read more: [Next.js Docs: `headers`](https://nextjs.org/docs/app/api-reference/functions/headers)
 */
export declare function headers(): Promise<ReadonlyHeaders>;

import { type ReadonlyHeaders } from '../web/spec-extension/adapters/headers'; /** * In this version of Next.js `headers()` returns a Promise however you can still reference the properties of the underlying Headers instance * synchronously to facilitate migration. The `UnsafeUnwrappedHeaders` type is added to your code by a codemod that attempts to automatically * updates callsites to reflect the new Promise return type. There are some cases where `headers()` cannot be automatically converted, namely * when it is used inside a synchronous function and we can't be sure the function can be made async automatically. In these cases we add an * explicit type case to `UnsafeUnwrappedHeaders` to enable typescript to allow for the synchronous usage only where it is actually necessary. * * You should should update these callsites to either be async functions where the `headers()` value can be awaited or you should call `headers()` * from outside and await the return value before passing it into this function. * * You can find instances that require manual migration by searching for `UnsafeUnwrappedHeaders` in your codebase or by search for a comment that * starts with `@next-codemod-error`. * * In a future version of Next.js `headers()` will only return a Promise and you will not be able to access the underlying Headers instance * without awaiting the return value first. When this change happens the type `UnsafeUnwrappedHeaders` will be updated to reflect that is it no longer * usable. * * This type is marked deprecated to help identify it as target for refactoring away. * * @deprecated */ export type UnsafeUnwrappedHeaders = ReadonlyHeaders; /** * This function allows you to read the HTTP incoming request headers in * [Server Components](https://nextjs.org/docs/app/building-your-application/rendering/server-components), * [Server Actions](https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations), * [Route Handlers](https://nextjs.org/docs/app/building-your-application/routing/route-handlers) and * [Middleware](https://nextjs.org/docs/app/building-your-application/routing/middleware). * * Read more: [Next.js Docs: `headers`](https://nextjs.org/docs/app/api-reference/functions/headers) */ export declare function headers(): Promise;