<commit_before>## Explanation of Build Files

> A rule of thumb: files that end in `common.js` are meant for built tools, files that do not end in `common.js` are meant for direct browser usage.

- ### vue.js

  The full (compiler-included) browser build. This is the build you can just include with a script tag:

  ```
  <script src="https://unkpg.com/vue/dist/vue.js"><script>
  ```

  Note that this build is hard-coded to development mode.

- ### vue.min.js

  Same as `vue.js`, but minified AND is hard-coded to production mode (with runtime checks and warnings stripped).

- ### vue.common.js

  The full (compiler-included) CommonJS build. This is the build intended to be used with a Node-compatible bundler, e.g. Webpack or Browserify.

  The difference between the browser build and the CommonJS build is that the latter preserves the `process.env.NODE_ENV` check for development/production modes (defaults to development mode). This gives you more control over what mode the code should run in:

  - When bundling for the browser, you can turn on production mode by using Webpack's [DefinePlugin](https://webpack.github.io/docs/list-of-plugins.html#defineplugin) to replace `process.env.NODE_ENV` with the `"production"` string literal:

    ``` js
    plugins: [
      new webpack.DefinePlugin({
        'process.env.NODE_ENV': '"production"'
      })
    ]
    ```
<commit_msg>Fix unkpg.com -> unpkg.com (#4460)<commit_after>## Explanation of Build Files

> A rule of thumb: files that end in `common.js` are meant for built tools, files that do not end in `common.js` are meant for direct browser usage.

- ### vue.js

  The full (compiler-included) browser build. This is the build you can just include with a script tag:

  ```
  <script src="https://unpkg.com/vue/dist/vue.js"></script>
  ```

  Note that this build is hard-coded to development mode.

- ### vue.min.js

  Same as `vue.js`, but minified AND is hard-coded to production mode (with runtime checks and warnings stripped).

- ### vue.common.js

  The full (compiler-included) CommonJS build. This is the build intended to be used with a Node-compatible bundler, e.g. Webpack or Browserify.

  The difference between the browser build and the CommonJS build is that the latter preserves the `process.env.NODE_ENV` check for development/production modes (defaults to development mode). This gives you more control over what mode the code should run in:

  - When bundling for the browser, you can turn on production mode by using Webpack's [DefinePlugin](https://webpack.github.io/docs/list-of-plugins.html#defineplugin) to replace `process.env.NODE_ENV` with the `"production"` string literal:

    ``` js
    plugins: [
      new webpack.DefinePlugin({
        'process.env.NODE_ENV': '"production"'
      })
    ]
    ```

{'fraction_non_alphanumeric': 0.09985734664764621, 'fraction_numerical': 0.0014265335235378032, 'mean_word_length': 3.6210873146622733, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 10, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2679049', 'n_tokens_mistral': 816, 'n_tokens_neox': 779, 'n_words': 339}