Damiano
@Danielku15 any chance to use with ESM? The following does not work still: ```sh NODE_ENV=development node --experimental-specifier-resolution=node --loader ts-node/esm -r tsconfig-paths/register ./src/index.ts ```
@kibertoad I'd be glad to work on it, but before investing so much effort in it I'd like to ask you: is there an intention to actually push this from...
@kibertoad which tooling are you referring too? Just to share your experience/knowledge.
IPN simulator is broken, always returning `INVALID` when the same code in production returns `VERIFIED`. And my IPN script correctly sends back the processed the message to `https://ipnpb.sandbox.paypal.com/cgi-bin/webscr` when using...
@daslicht yeah, me too. Then verification of IPN message to `https://ipnpb.sandbox.paypal.com/cgi-bin/webscr` miserably fails. Same code of production, just calling sandbox url. We resorted testing with real transactions.
Issued here: https://github.com/Teamwork/node-auto-launch/issues/46 WIP here: https://github.com/Teamwork/node-auto-launch/pull/47#pullrequestreview-75935893
cc @lbltavares
It looks like directives are honored only if under the settings definition: ```json { "root": true, "parser": "@typescript-eslint/parser", "parserOptions": { "sourceType": "module", "ecmaVersion": 2022, "ecmaFeatures": { "jsx": true } },...
The `tailwindcss/no-custom-classname` is taking 2mins on my project as well. @francoismassart can you suggest an approach to mitigate this? Or is there any plan to do something about it? Thanks!