Files
vercel/packages/client/tests/paths.test.ts
Sean Massa 0490a7733b [tests] install root typescript version 4.9.5 and standardize on that version (#9858)
This add a root-level `typescript` version that matches the one used throughout for VS Code (and other IDEs) to use when browsing the code. After this PR merges, you will be able to set VS Code's TypeScript version to match the project's version.

This will remove issues where the IDE says TypeScript compilation is good to go, but `pnpm build` disagrees.

If there's a better way to allow this, please suggest it!

---

To enable:

<img width="849" alt="Screenshot 2023-04-25 at 4 28 22 PM" src="https://user-images.githubusercontent.com/41545/234408245-205b3260-7b1d-4c43-a531-d616915dbefb.png">

Then:

<img width="1015" alt="Screenshot 2023-04-25 at 4 29 20 PM" src="https://user-images.githubusercontent.com/41545/234408271-4e7b4ec8-0be3-4743-afd7-813a267c0756.png">
2023-04-27 08:13:53 +00:00

45 lines
1014 B
TypeScript

import { generateNewToken } from './common';
import { createDeployment } from '../src/index';
describe('path handling', () => {
let token = '';
beforeEach(async () => {
token = await generateNewToken();
});
it('will fali with a relative path', async () => {
try {
await createDeployment(
{
token,
path: './fixtures/v2/now.json',
},
{
name: 'now-client-tests-v2',
}
);
} catch (_error: unknown) {
const error = _error as NodeJS.ErrnoException;
expect(error.code).toEqual('invalid_path');
}
});
it('will fali with an array of relative paths', async () => {
try {
await createDeployment(
{
token,
path: ['./fixtures/v2/now.json'],
},
{
name: 'now-client-tests-v2',
}
);
} catch (_error: unknown) {
const error = _error as NodeJS.ErrnoException;
expect(error.code).toEqual('invalid_path');
}
});
});