<div id="readability-page-1" class="page"><div><h2>타입스크립트, 바벨 npm 설정</h2>
<h2>패키지 설치</h2>
<h3>테스트 관련</h3>
<pre><code>$ npm install --save-dev jest @types/jest</code></pre><h3>타입스크립트, 바벨관련</h3>
<pre><code>$ npm install --save-dev typescript</code></pre><h2>NPM 셋업</h2>
<h3>설정파일 생성</h3>
<p>설치 중간에 test command를 입력하라는 prompt가 나오면 <code>jest</code>로 입력한다. <code>npm run test</code> 명령어를 통해 테스트를 수행 할 수 있게 만들기 위한 부분이다.</p>
<pre><code>$ npm init</code></pre><h3>스크립트 추가</h3>
<ul>
<li>package.json</li>
</ul>
<pre><code>{
  "name": "class-enum",
  "version": "0.0.1",
  "description": "class enum",
  "main": "index.js",
  "scripts": {
    "test": "jest",
    "compile": "tsc",
    "build": "jest &amp;&amp; tsc"
  },
    ...
    ...
}</code></pre><h2>폴더 생성</h2>
<pre><code>$ mkdir src tests &amp;&amp; touch ./src/index.ts</code></pre><h2>나의 모듈 생성</h2>
<p>내가 만들고싶은 모듈을 작성한다.</p>
<ul>
<li>./src/index.ts</li>
</ul>
<pre><code>export default class ClassEnum {
...
}</code></pre><h2>타입스크립트 설정파일 생성</h2>
<p>아래 명령어를 입력하면 <code>tsconfig.json</code> 파일이 생성된다. 필요없는 주석은 삭제한다.</p>
<pre><code>$ ./node_modules/typescript/bin/tsc --init</code></pre><pre><code>{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "outDir": "./dist",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true
  },
  "include": [
    "src/**/*",
    "tests/**/*"
  ]
}</code></pre><h2>테스트 생성 및 실행</h2>
<p>테스트 파일을 하나 만들어 <code>jest</code>가 잘 실행되는지 확인한다.</p>
<ul>
<li>./tests/index.test.ts</li>
</ul>
<pre><code>import ClassEnum from "../src/index"

test('always true', () =&gt; {
    expect(1).toBe(1);
});</code></pre><pre><code>$ npm run test</code></pre><h3>오류 발생</h3>
<pre><code>&gt; class-enum@0.0.1 test
&gt; jest

 FAIL  tests/index.test.ts
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/hodolman/work/class-enum/tests/index.test.ts:1
    ({"Object.&lt;anonymous&gt;":function(module,exports,require,__dirname,__filename,jest){import ClassEnum from "../src/index";
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)</code></pre><h3>바벨 &amp; 바벨 타입스크립트 설치</h3>
<pre><code>$ npm install --save-dev @babel/core @babel/cli @babel/preset-typescript</code></pre><h3>바벨 설정파일 생성</h3>
<ul>
<li>babel.config.js</li>
</ul>
<pre><code>module.exports = {
  presets: [
    ['@babel/preset-env', {targets: {node: 'current'}}],
    '@babel/preset-typescript',
  ],
};</code></pre><h2>테스트 실행</h2>
<pre><code>$ npm run test
&gt; class-enum@0.0.1 test
&gt; jest

 PASS  tests/index.test.ts
  ✓ always true (1 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        0.775 s
Ran all test suites.</code></pre></div></div>

호돌맨의 블로그

JuHyun Lee

타입스크립트, 바벨 npm 설정
패키지 설치
테스트 관련
$ npm install --save-dev jest @types/jest
타입스크립트, 바벨관련
$ npm install --save-dev typescript
NPM 셋업
설정파일 생성
설치 중간에 test command를 입력하라는 prompt가 나오면 jest로 입력한다. npm run test 명령어를 통해 테스트를 수행 할 수 있게 만들기 위한 부분이다.
$ npm init
스크립트 추가
package.json
{
  "name": "class-enum",
  "version": "0.0.1",
  "description": "class enum",
  "main": "index.js",
  "scripts": {
    "test": "jest",
    "compile": "tsc",
    "build": "jest && tsc"
  },
    ...
    ...
}
폴더 생성
$ mkdir src tests && touch ./src/index.ts
나의 모듈 생성
내가 만들고싶은 모듈을 작성한다.
./src/index.ts
export default class ClassEnum {
...
}
타입스크립트 설정파일 생성
아래 명령어를 입력하면 tsconfig.json 파일이 생성된다. 필요없는 주석은 삭제한다.
$ ./node_modules/typescript/bin/tsc --init
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "outDir": "./dist",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true
  },
  "include": [
    "src/**/*",
    "tests/**/*"
  ]
}
테스트 생성 및 실행
테스트 파일을 하나 만들어 jest가 잘 실행되는지 확인한다.
./tests/index.test.ts
import ClassEnum from "../src/index"
test('always true', () => {
    expect(1).toBe(1);
});
$ npm run test
오류 발생
> class-enum@0.0.1 test
> jest
 FAIL  tests/index.test.ts
  ● Test suite failed to run
    Jest encountered an unexpected token
    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.
    By default "node_modules" folder is ignored by transformers.
    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation
    Details:
    /Users/hodolman/work/class-enum/tests/index.test.ts:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import ClassEnum from "../src/index";
                                                                                      ^^^^^^
    SyntaxError: Cannot use import statement outside a module
      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
바벨 & 바벨 타입스크립트 설치
$ npm install --save-dev @babel/core @babel/cli @babel/preset-typescript
바벨 설정파일 생성
babel.config.js
module.exports = {
  presets: [
    ['@babel/preset-env', {targets: {node: 'current'}}],
    '@babel/preset-typescript',
  ],
};
테스트 실행
$ npm run test
> class-enum@0.0.1 test
> jest
 PASS  tests/index.test.ts
  ✓ always true (1 ms)
Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        0.775 s
Ran all test suites.

typescript, babel, jest 모듈 환경 구성

댓글