diff --git a/.babelrc b/.babelrc deleted file mode 100644 index a63facd..0000000 --- a/.babelrc +++ /dev/null @@ -1,35 +0,0 @@ -{ - "presets": [ - [ - "env", - { - "useBuiltIns": true, - "targets": { - "node": "6.9.0" - }, - "exclude": [ - "transform-async-to-generator", - "transform-regenerator" - ] - } - ] - ], - "plugins": [ - [ - "transform-object-rest-spread", - { - "useBuiltIns": true - } - ] - ], - "env": { - "test": { - "presets": [ - "env" - ], - "plugins": [ - "transform-object-rest-spread" - ] - } - } -} diff --git a/.circleci/config.yml b/.circleci/config.yml deleted file mode 100644 index f43400d..0000000 --- a/.circleci/config.yml +++ /dev/null @@ -1,161 +0,0 @@ -unit_tests: &unit_tests - steps: - - checkout - - setup_remote_docker - - restore_cache: - key: dependency-cache-{{ checksum "package-lock.json" }} - - run: - name: NPM Rebuild - command: npm install - - run: - name: Run unit tests. - command: npm run ci:test -canary_tests: &canary_tests - steps: - - checkout - - setup_remote_docker - - restore_cache: - key: dependency-cache-{{ checksum "package-lock.json" }} - - run: - name: NPM Rebuild - command: npm install - - run: - name: Install Webpack Canary - command: npm i --no-save webpack@next - - run: - name: Run unit tests. - command: npm run ci:test - -version: 2 -jobs: - dependency_cache: - docker: - - image: webpackcontrib/circleci-node-base:latest - steps: - - checkout - - setup_remote_docker - - restore_cache: - key: dependency-cache-{{ checksum "package-lock.json" }} - - run: - name: Install Dependencies - command: npm install - - save_cache: - key: dependency-cache-{{ checksum "package-lock.json" }} - paths: - - ./node_modules - - node8-latest: - docker: - - image: webpackcontrib/circleci-node8:latest - steps: - - checkout - - setup_remote_docker - - restore_cache: - key: dependency-cache-{{ checksum "package-lock.json" }} - - run: - name: NPM Rebuild - command: npm install - - run: - name: Run unit tests. - command: npm run ci:coverage - - run: - name: Submit coverage data to codecov. - command: bash <(curl -s https://codecov.io/bash) - when: on_success - node6-latest: - docker: - - image: webpackcontrib/circleci-node6:latest - <<: *unit_tests - node9-latest: - docker: - - image: webpackcontrib/circleci-node9:latest - <<: *unit_tests - node8-canary: - docker: - - image: webpackcontrib/circleci-node8:latest - <<: *canary_tests - analysis: - docker: - - image: webpackcontrib/circleci-node-base:latest - steps: - - checkout - - setup_remote_docker - - restore_cache: - key: dependency-cache-{{ checksum "package-lock.json" }} - - run: - name: NPM Rebuild - command: npm install - - run: - name: Run linting. - command: npm run lint - - run: - name: Run NSP Security Check. - command: npm run security - - run: - name: Validate Commit Messages - command: npm run ci:lint:commits - publish: - docker: - - image: webpackcontrib/circleci-node-base:latest - steps: - - checkout - - setup_remote_docker - - restore_cache: - key: dependency-cache-{{ checksum "package-lock.json" }} - - run: - name: NPM Rebuild - command: npm install - - run: - name: Validate Commit Messages - command: npm run release:validate - - run: - name: Publish to NPM - command: printf "noop running conventional-github-releaser" - -version: 2.0 -workflows: - version: 2 - validate-publish: - jobs: - - dependency_cache - - node6-latest: - requires: - - dependency_cache - filters: - tags: - only: /.*/ - - analysis: - requires: - - dependency_cache - filters: - tags: - only: /.*/ - - node8-latest: - requires: - - analysis - - node6-latest - filters: - tags: - only: /.*/ - - node9-latest: - requires: - - analysis - - node6-latest - filters: - tags: - only: /.*/ - - node8-canary: - requires: - - analysis - - node6-latest - filters: - tags: - only: /.*/ - - publish: - requires: - - node8-latest - - node9-latest - filters: - branches: - only: - - master diff --git a/.editorconfig b/.editorconfig index 45946ea..9f89f36 100644 --- a/.editorconfig +++ b/.editorconfig @@ -9,5 +9,5 @@ insert_final_newline = true trim_trailing_whitespace = true [*.md] -insert_final_newline = false +insert_final_newline = true trim_trailing_whitespace = false diff --git a/.eslintignore b/.eslintignore index 8225baa..51d168b 100644 --- a/.eslintignore +++ b/.eslintignore @@ -1,2 +1,5 @@ -/node_modules +/coverage /dist +/node_modules +/test/fixtures +/test/output diff --git a/.eslintrc.js b/.eslintrc.js index f5064a3..095ce2a 100644 --- a/.eslintrc.js +++ b/.eslintrc.js @@ -1,11 +1,4 @@ module.exports = { root: true, - plugins: ['prettier'], - extends: ['@webpack-contrib/eslint-config-webpack'], - rules: { - 'prettier/prettier': [ - 'error', - { singleQuote: true, trailingComma: 'es5', arrowParens: 'always' }, - ], - }, + extends: ['@webpack-contrib/eslint-config-webpack', 'prettier'], }; diff --git a/.gitattributes b/.gitattributes index 70df4c9..8b6b1c8 100644 --- a/.gitattributes +++ b/.gitattributes @@ -1,3 +1,4 @@ -package-lock.json -diff * text=auto bin/* eol=lf +package-lock.json -diff +yarn.lock -diff diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md deleted file mode 100644 index c8c9382..0000000 --- a/.github/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,46 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. - -## Our Standards - -Examples of behavior that contributes to creating a positive environment include: - -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - -Examples of unacceptable behavior by participants include: - -* The use of sexualized language or imagery and unwelcome sexual attention or advances -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or electronic address, without explicit permission -* Other conduct which could reasonably be considered inappropriate in a professional setting - -## Our Responsibilities - -Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. - -Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. - -## Scope - -This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at jgkurian@me.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. - -Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] - -[homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/ diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md new file mode 100644 index 0000000..4a29d18 --- /dev/null +++ b/.github/CONTRIBUTING.md @@ -0,0 +1,160 @@ +# Contributing in @webpack-contrib + +We'd always love contributions to further improve the webpack / webpack-contrib ecosystem! +Here are the guidelines we'd like you to follow: + +- [Questions and Problems](#question) +- [Issues and Bugs](#issue) +- [Feature Requests](#feature) +- [Pull Request Submission Guidelines](#submit-pr) +- [Commit Message Conventions](#commit) + +## Got a Question or Problem? + +Please submit support requests and questions to StackOverflow using the tag [[webpack]](http://stackoverflow.com/tags/webpack). +StackOverflow is better suited for this kind of support though you may also inquire in [Webpack Gitter](https://gitter.im/webpack/webpack). +The issue tracker is for bug reports and feature discussions. + +## Found an Issue or Bug? + +Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available. + +We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we ask that you to provide a minimal reproduction scenario (github repo or failing test case). Having a live, reproducible scenario gives us a wealth of important information without going back & forth to you with additional questions like: + +- version of Webpack used +- version of the loader / plugin you are creating a bug report for +- the use-case that fails + +A minimal reproduce scenario allows us to quickly confirm a bug (or point out config problems) as well as confirm that we are fixing the right problem. + +We will be insisting on a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more bugs. We understand that sometimes it might be hard to extract essentials bits of code from a larger code-base but we really need to isolate the problem before we can fix it. + +Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that doesn't have enough info to be reproduced. + +## Feature Requests? + +You can _request_ a new feature by creating an issue on Github. + +If you would like to _implement_ a new feature, please submit an issue with a proposal for your work `first`, to be sure that particular makes sense for the project. + +## Pull Request Submission Guidelines + +Before you submit your Pull Request (PR) consider the following guidelines: + +- Search Github for an open or closed PR that relates to your submission. You don't want to duplicate effort. +- Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit). Adherence to these conventions is necessary because release notes are automatically generated from these messages. +- Fill out our `Pull Request Template`. Your pull request will not be considered if it is ignored. +- Please sign the `Contributor License Agreement (CLA)` when a pull request is opened. We cannot accept your pull request without this. Make sure you sign with the primary email address associated with your local / github account. + +## Webpack Contrib Commit Conventions + +Each commit message consists of a **header**, a **body** and a **footer**. The header has a special +format that includes a **type**, a **scope** and a **subject**: + +``` +(): + + + +