wellwelwel / poku Goto Github PK

In fact, all the lines are covered, but not for tests. It's for use, due to my helper tools for rewriting files and ensuring compatibility with Node.js in older versions, Bun and Deno.

To see the actual coverage status, just run npm run test:c8. This will use Docker to ensure that only the final files are tested, but Codecov shows "unknown" status and throws an error when uploading these coverage results for some reason.

Sorry about that, as soon as possible I would like to figure it out 💙

Inspiration

Source: https://youtu.be/iDaBo7ge604?si=x8hWjOH8ffHHOJ_6&t=2674
Credits to @ErickWendel 🇧🇷

In the same approach for assert, allow users to use all the native approaches in Poku:

From (Node.js homepage):

// tests.mjs
import assert from 'node:assert';
import test from 'node:test';

test('that 1 is equal 1', () => {
  assert.strictEqual(1, 1);
});

test('that throws as 1 is not equal 2', () => {
  // throws an exception because 1 != 2
  assert.strictEqual(1, 2);
});

// run with `node tests.mjs`

To (Poku):

// tests.mjs
import { test, assert } from 'poku';

test('that 1 is equal 1', () => {
  assert.strictEqual(1, 1);
});

test('that throws as 1 is not equal 2', () => {
  // throws an exception because 1 != 2
  assert.strictEqual(1, 2);
});

// run with `npx poku tests.mjs`

• Same idea for describe and it.

Sometimes, the file path is not parsed when using Poku's assert with Bun.

Descrição da issue

Basicamente quando eu tento executar os testes utilizando o Bun como runtime ele funciona normalmente, mas ao importar algo relacionado ao Bun dentro do arquivo de teste, o poku quebra, simplesmente não executa e crasha sem mensagem de erro.

Primeiramente eu comecei tentando importar o mock do jest de dentro do "bun:test" e crashava, ai tentei importar outras coisas de dentro do bun, de outras bibliotecas do bun e crashava. Não importa o que eu importe, se for diretamente do bun, crasha.

Ambiente

WSL2 Rodando Arch Linux

Como reproduzir

Crie um arquivo de teste, no meu caso, eu criei da seguinte forma:

• | tests
  • | poku.test.ts

Depois dentro dele, coloque um assert pra testar e antes dele, importe qualquer lib do bun.
Exemplo:

import { assert } from "poku";
import { Database } from "bun:sqlite";

assert(true, "Poku test");

O output desse teste é esse:

Eu imagino que esse erro seja originado porque os testes são executados com node ao invés do próprio bun, (talvez alguma configuração que eu não soube fazer?).
Quando é usado Typescript, os arquivos são executados com npx tsx e com Javascript, node.
Como ele executa com node e não com o próprio Bun, imagino eu que quebre na hora de importar algo diretamente do Bun.

The startScript currently doesn't work for Bun and Deno.

How the startScript works?

• It will use spawn to start your script in a background process
• By using .end(), the current process and all its sub-processes will be terminated
• By forcing finish (Ctrl+C), it will terminate all the background process and all its sub-processes

Expected Behavior

Using Node.js, it will close all subprocesses when closing the main process.

The Issue

However, on Bun and Deno, when the main process is finished, all subprocesses remain open and only the main process is closed.

PRs are welcome 🤝

By default Poku uses --allow-run, --allow-env, --allow-read that are required to everything works fine, but it needs to improve a way to pass or replace the permissions.

Currently, functions are displayed as it is ("() => {}") and Regex are converted to string ("/rule/"), but the same doesn't is valid when they are inside an array, that shows function as "null" and Regex as "{}".

Ideas

CLI

npx poku --parallel --concurrency=3

API (in-code)

await poku(['.'], {
  parallel: true,
  concurrency: 3,
});

Keeping compatibility for previous versions

Use default value as 0 (no limit).