UNPKG

@practica/create-node-app

Version:

Create Node.js app that is packed with best practices AND strive for simplicity

github.com/bestpractices/practica

practicajs/practica

82 lines (64 loc) • 5.04 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
> @practica/logger@0.0.5 test > jest --forceExit Determining test suites to run...      RUNS  test/index.test.ts    ts-jest[ts-jest-transformer] (WARN) Got a `.js` file to compile while `allowJs` option is not set to `true` (file: /Users/goldbergyoni/solutions/practica/src/code-templates/libraries/global-context/.dist/index.js). To fix this: - if you want TypeScript to process JS files, set `allowJs` to `true` in your TypeScript config (usually tsconfig.json) - if you do not want TypeScript to process your `.js` files, in your Jest config change the `transform` key which value is `ts-jest` so that it does not match `.js` files anymore  RUNS  test/index.test.ts    ts-jest[ts-jest-transformer] (WARN) Got a `.js` file to compile while `allowJs` option is not set to `true` (file: /Users/goldbergyoni/solutions/practica/src/code-templates/libraries/global-context/.dist/src/context.js). To fix this: - if you want TypeScript to process JS files, set `allowJs` to `true` in your TypeScript config (usually tsconfig.json) - if you do not want TypeScript to process your `.js` files, in your Jest config change the `transform` key which value is `ts-jest` so that it does not match `.js` files anymore  RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts      RUNS  test/index.test.ts     PASS  test/index.test.ts  RUNS  test/index.test.ts     logger  RUNS  test/index.test.ts     ✓ When no explicit configuration is set, info logs are written (4 ms)  RUNS  test/index.test.ts     ✓ When log level is DEBUG and logger emits INFO statement, then stdout contains the entry (1 ms)  RUNS  test/index.test.ts     ✓ When logger is configured and then re-configured, then the new config applies  RUNS  test/index.test.ts     ✓ When log level is ERROR and logger emits INFO statement, then nothing is written (1 ms)  RUNS  test/index.test.ts     ✓ When configuring for pretty-print, then its written to stdout  RUNS  test/index.test.ts     ✓ it should print the passed metadata  RUNS  test/index.test.ts     context  RUNS  test/index.test.ts     ✓ it should print the current context (1 ms)  RUNS  test/index.test.ts     ✓ it should merge with current context (3 ms)  RUNS  test/index.test.ts     ✓ it should override current context (1 ms)  RUNS  test/index.test.ts      RUNS  test/index.test.ts    Test Suites: 1 passed, 1 total Tests: 9 passed, 9 total Snapshots: 0 total Time: 4.108 s Ran all test suites. Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?