Spectrum is now read-only. Learn more about the decision in our official announcement.


Use with Typescript

March 29, 2019 at 12:00pm

Use with Typescript

March 29, 2019 at 12:00pm
Hi, nice project. Is there a way to use it with typescript, maybe by starting it with an option to change the testMatch?

March 31, 2019 at 8:44am
Majestic should support out of the box. Majestic doesn't rely on the testMatch pattern internally. We rely on the --listTests command to get the test files. I'm curious to know where this is failing?

April 1, 2019 at 12:21pm
No tests are found but it also starts with an error ⚡ Majestic v1.2.23 is running at http://localhost:4000 (node:28450) UnhandledPromiseRejectionWarning: Error: spawn /home/aure/.nvm/versions/node/v10.15.1/lib/node_modules/majestic/dist/server/xdg-open ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) at Function.Module.runMain (internal/modules/cjs/loader.js:745:11) at startup (internal/bootstrap/node.js:283:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3) (node:28450) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) (node:28450) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I will have a look and ask if I cannot solve it.

April 2, 2019 at 12:35pm
The startup error should be fixed with
Let me know if I can help after you looking into it