<commit_before># Release history

### 5.0.0 XXX

- use `--npm-options` to pass additional options to NPM when installing packages. Useful to specify behaviour for package locking.
- packaging using NPM 6 is now faster as audits are turned off by default
- packaging support for NPM 5 and 6 using relative file dependencies -- this previously worked only with NPM 3 because NPM 5 uses symbolic links for relative references
- upload size optimised using for NPM 5 and 6 by deduping dependencies after packaging
- use `--post-package-script=<NPM SCRIPT NAME>` with `claudia create` or `claudia update` to execute a custom post-package step to clean up resources, optimise package size etc. This runs after all validations are complete, and development dependencies are not available at this stage... but you can use npm to uninstall utility tools as part of this step if needed.
- new command. [`claudia pack`](docs/pack.md) just packages the files, correctly handling NPM dependencies, without deploying anywhere. Useful for troubleshooting, or if you want to deploy to Lambda using some other tool but get Claudia to prepare the package for you. This is specially useful for CloudFormation deployments if you want to use NPM 5 or 6. The command works with any Node.js Lambda project, not just Claudia-specific ones. 
- claudia automatically fixes file access permissions in your package that would prevent Lambda from running code.
- NPM output is now directly written to the console, rather than a separate log file, to make packaging errors more obvious

### 4.0.0 9 April 2018

- compatibility with Node.js 8.10 and NPM 5<commit_msg>release info for 5.x<commit_after># Release history

### 5.0.0 7 June 2018

- use `--npm-options` to pass additional options to NPM when installing packages. Useful to specify behaviour for package locking.
- packaging using NPM 6 is now faster as audits are turned off by default
- packaging support for NPM 5 and 6 using relative file dependencies -- this previously worked only with NPM 3 because NPM 5 uses symbolic links for relative references
- upload size optimised using for NPM 5 and 6 by deduping dependencies after packaging
- use `--post-package-script=<NPM SCRIPT NAME>` with `claudia create` or `claudia update` to execute a custom post-package step to clean up resources, optimise package size etc. This runs after all validations are complete, and development dependencies are not available at this stage... but you can use npm to uninstall utility tools as part of this step if needed.
- new command. [`claudia pack`](docs/pack.md) just packages the files, correctly handling NPM dependencies, without deploying anywhere. Useful for troubleshooting, or if you want to deploy to Lambda using some other tool but get Claudia to prepare the package for you. This is specially useful for CloudFormation deployments if you want to use NPM 5 or 6. The command works with any Node.js Lambda project, not just Claudia-specific ones. 
- claudia automatically fixes file access permissions in your package that would prevent Lambda from running code.
- NPM output is now directly written to the console, rather than a separate log file, to make packaging errors more obvious

### 4.0.0 9 April 2018

- compatibility with Node.js 8.10 and NPM 5
{'fraction_non_alphanumeric': 0.04715546090660176, 'fraction_numerical': 0.016428354122299968, 'mean_word_length': 4.294685990338165, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, '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': '557835', 'n_tokens_mistral': 856, 'n_tokens_neox': 785, 'n_words': 502}