Repository: simonepri/sympact Branch: master Commit: ff60a2325afa Files: 20 Total size: 38.9 KB Directory structure: gitextract_ri8w7s5_/ ├── .appveyor.yml ├── .codecov.yml ├── .editorconfig ├── .gitattributes ├── .github/ │ ├── code-of-conduct.md │ ├── contributing.md │ ├── issue-template.md │ └── pull-request-template.md ├── .gitignore ├── .npmrc ├── .travis.yml ├── cli.js ├── index.js ├── lib/ │ ├── profiler.js │ ├── vm.js │ └── worker.js ├── license ├── package.json ├── readme.md └── test.js ================================================ FILE CONTENTS ================================================ ================================================ FILE: .appveyor.yml ================================================ build: off version: '{build}' environment: matrix: - nodejs_version: '8' - nodejs_version: '10' platform: - x86 - x64 cache: - node_modules install: - ps: Install-Product node $env:nodejs_version - npm install test_script: - node --version - npm --version - npm test after_test: - npx codecov ================================================ FILE: .codecov.yml ================================================ parsers: javascript: enable_partials: yes ================================================ FILE: .editorconfig ================================================ root = true [*] indent_size = 2 indent_style = space end_of_line = lf charset = utf-8 trim_trailing_whitespace = true insert_final_newline = true ================================================ FILE: .gitattributes ================================================ * text=auto *.js text eol=lf ================================================ FILE: .github/code-of-conduct.md ================================================ # 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 [simonepri@outlook.com](mailto:simonepri@outlook.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/ ================================================ FILE: .github/contributing.md ================================================ # Contributing First and foremost, thank you! We appreciate that you want to contribute to this project, your time is valuable, and your contributions mean a lot to us. ## Important! By contributing to this project, you: - Agree that you have authored 100% of the content - Agree that you have the necessary rights to the content - Agree that you have received the necessary permissions from your employer to make the contributions (if applicable) - Agree that the content you contribute may be provided under the Project license(s) ## Getting started **What does "contributing" mean?** Creating an issue is the simplest form of contributing to a project. But there are many ways to contribute, including the following: - Updating or correcting documentation - Feature requests - Bug reports If you'd like to learn more about contributing in general, the [Guide to Idiomatic Contributing](https://github.com/jonschlinkert/idiomatic-contributing) has a lot of useful information. ## Issues ### Before creating an issue Please try to determine if the issue is caused by an underlying library, and if so, create the issue there. Sometimes this is difficult to know. We only ask that you attempt to give a reasonable attempt to find out. Oftentimes the readme will have advice about where to go to create issues. Try to follow these guidelines - **Avoid creating issues for implementation help**. It's much better for discoverability, SEO, and semantics - to keep the issue tracker focused on bugs and feature requests - to ask implementation-related questions on [so](stackoverflow.com) - **Investigate the issue**: - **Check the readme** - oftentimes you will find notes about creating issues, and where to go depending on the type of issue. - Create the issue in the appropriate repository. ### Creating an issue Please be as descriptive as possible when creating an issue. Give us the information we need to successfully answer your question or address your issue by answering the following in your issue: - **version**: please note the version of the project are you using - **extensions, plugins, helpers, etc** (if applicable): please list any extensions you're using - **error messages**: please paste any error messages into the issue, or a [gist](https://gist.github.com/) ### Closing issues The original poster or the maintainer's of the project may close an issue at any time. Typically, but not exclusively, issues are closed when: - The issue is resolved - The project's maintainers have determined the issue is out of scope - An issue is clearly a duplicate of another issue, in which case the duplicate issue will be linked. - A discussion has clearly run its course ## Next steps **Tips for creating idiomatic issues** Spending just a little extra time to review best practices and brush up on your contributing skills will, at minimum, make your issue easier to read, easier to resolve, and more likely to be found by others who have the same or similar issue in the future. At best, it will open up doors and potential career opportunities by helping you be at your best. The following resources were hand-picked to help you be the most effective contributor you can be: - The [Guide to Idiomatic Contributing](https://github.com/jonschlinkert/idiomatic-contributing) is a great place for newcomers to start, but there is also information for experienced contributors there. - Take some time to learn basic markdown. We can't stress this enough. Don't start pasting code into GitHub issues before you've taken a moment to review this [markdown cheatsheet](https://gist.github.com/jonschlinkert/5854601) - The GitHub guide to [basic markdown](https://help.github.com/articles/markdown-basics/) is another great markdown resource. - Learn about [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). And if you want to really go above and beyond, read [mastering markdown](https://guides.github.com/features/mastering-markdown/). At the very least, please try to: - Use backticks to wrap code. This ensures that it retains its formatting and isn't modified when it's rendered by GitHub, and makes the code more readable to others - When applicable, use syntax highlighting by adding the correct language name after the first "code fence" ================================================ FILE: .github/issue-template.md ================================================ ## I'm submitting a - [ ] bug report - [ ] feature request - [ ] support request => Please do not submit support request here, see note at the top of this template. ## Checklist - [ ] Searched both open and closed issues for duplicates of this issue - [ ] Title adequately and *concisely* reflects the feature or the bug ## Information ================================================ FILE: .github/pull-request-template.md ================================================ ## Checklist - [ ] All tests are passing - [ ] New tests were created to address changes in pr (and tests are passing) - [ ] Updated README and/or documentation, if necessary - [ ] Added myself / the `contributors` array in package.json ## Changes ================================================ FILE: .gitignore ================================================ # Created by https://www.gitignore.io/api/linux,macos,windows,node ### Linux ### *~ # temporary files which can be created if a process still has a handle open of a deleted file .fuse_hidden* # KDE directory preferences .directory # Linux trash folder which might appear on any partition or disk .Trash-* # .nfs files are created when an open file is removed but is still being accessed .nfs* ### macOS ### *.DS_Store .AppleDouble .LSOverride # Icon must end with two \r Icon # Thumbnails ._* # Files that might appear in the root of a volume .DocumentRevisions-V100 .fseventsd .Spotlight-V100 .TemporaryItems .Trashes .VolumeIcon.icns .com.apple.timemachine.donotpresent # Directories potentially created on remote AFP share .AppleDB .AppleDesktop Network Trash Folder Temporary Items .apdisk ### Node ### # Logs logs *.log npm-debug.log* yarn-debug.log* yarn-error.log* # Runtime data pids *.pid *.seed *.pid.lock # Directory for instrumented libs generated by jscoverage/JSCover lib-cov # Coverage directory used by tools like istanbul coverage # nyc test coverage .nyc_output # Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files) .grunt # Bower dependency directory (https://bower.io/) bower_components # node-waf configuration .lock-wscript # Compiled binary addons (http://nodejs.org/api/addons.html) build/Release # Dependency directories node_modules/ jspm_packages/ # Typescript v1 declaration files typings/ # Optional npm cache directory .npm # Optional eslint cache .eslintcache # Optional REPL history .node_repl_history # Output of 'npm pack' *.tgz # Yarn Integrity file .yarn-integrity # dotenv environment variables file .env ### Windows ### # Windows thumbnail cache files Thumbs.db ehthumbs.db ehthumbs_vista.db # Folder config file Desktop.ini # Recycle Bin used on file shares $RECYCLE.BIN/ # Windows Installer files *.cab *.msi *.msm *.msp # Windows shortcuts *.lnk # End of https://www.gitignore.io/api/linux,macos,windows,node ================================================ FILE: .npmrc ================================================ package-lock=false loglevel=silent ================================================ FILE: .travis.yml ================================================ sudo: false language: node_js node_js: - '8' - '10' os: - linux - osx cache: directories: - node_modules script: - node --version - npm --version - npm test after_test: - npx codecov ================================================ FILE: cli.js ================================================ #!/usr/bin/env node /* eslint-disable promise/prefer-await-to-then */ 'use strict'; const si = require('systeminformation'); const chalk = require('chalk'); const meow = require('meow'); const logSymbols = require('log-symbols'); const updateNotifier = require('update-notifier'); const Table = require('easy-table'); const impact = require('.'); const cli = meow( ` Usage $ impact