db-migrate 0.11.7 → 0.11.11

package/CHANGELOG.md

@@ -1,3 +1,29 @@
+## [0.11.7](https://github.com/db-migrate/node-db-migrate/compare/v0.11.6...v0.11.7) (2020-04-14)
+
+
+### Bug Fixes
+
+* **vuln:** backport [#679](https://github.com/db-migrate/node-db-migrate/issues/679) ([8b5beac](https://github.com/db-migrate/node-db-migrate/commit/8b5beac))
+
+
+### Features
+
+* **staticLoader:** a static loader to support packaging ([e183046](https://github.com/db-migrate/node-db-migrate/commit/e183046))
+
+
+
+## [0.11.6](https://github.com/db-migrate/node-db-migrate/compare/v0.11.5...v0.11.6) (2019-06-08)
+
+
+### Bug Fixes
+
+* **cwd:** addition of cwd missed function definition ([fae85cf](https://github.com/db-migrate/node-db-migrate/commit/fae85cf))
+* **plugin:** allow no package.json ([f27dce0](https://github.com/db-migrate/node-db-migrate/commit/f27dce0))
+* **plugin:** handle non existent dependencies and improve UX ([006ef5e](https://github.com/db-migrate/node-db-migrate/commit/006ef5e)), closes [#628](https://github.com/db-migrate/node-db-migrate/issues/628)
+* **plugin:** respect options cwd ([#618](https://github.com/db-migrate/node-db-migrate/issues/618)) ([3dae762](https://github.com/db-migrate/node-db-migrate/commit/3dae762))
+
+
+
 ## [0.11.6](https://github.com/db-migrate/node-db-migrate/compare/v0.11.5...v0.11.6) (2019-06-08)
 
 

package/lib/commands/generated.js

@@ -17,7 +17,6 @@ const files = {
   "index": require('./index.js'),
   "on-complete": require('./on-complete.js'),
   "run": require('./run.js'),
-  "run": require('./run.js.orig'),
   "seed": require('./seed.js'),
   "set-default-argv": require('./set-default-argv.js'),
   "sync": require('./sync.js'),

package/lib/commands/run.js

@@ -7,7 +7,6 @@ var transition;
 function run (internals, config) {
   const { load } = internals;
   const transition = load('transition');
-  console.log('hello');
   var action = internals.argv._.shift();
   var folder = action.split(':');
 

package/lib/commands/set-default-argv.js

@@ -124,7 +124,6 @@ module.exports = function (internals, isModule) {
   internals.argv.config = internals.argv.configFile || _config;
 
   if (internals.argv.version) {
-    console.log(internals.argv.version);
     console.log(internals.dbm.version);
     process.exit(0);
   }

package/package.json

@@ -31,7 +31,7 @@
     "programable",
     "api"
   ],
-  "version": "0.11.7",
+  "version": "0.11.11",
   "engines": {
     "node": ">=8.0.0"
   },
@@ -76,6 +76,10 @@
     "rimraf": "^2.6.2",
     "sinon": "^4.1.2"
   },
+  "funding": {
+    "type": "opencollective",
+    "url": "https://opencollective.com/node-db-migrate"
+  },
   "scripts": {
     "prepublishOnly": "node generateLoader.js",
     "pretest": "eslint *.js lib/*.js test/*.js bin/*",

package/.eslintrc

@@ -1,8 +0,0 @@
-{
-  "extends": "standard",
-  "rules": {
-    "semi": ["error", "always"],
-    "no-unused-vars": "warn",
-    "quotes": ["error", "single", { "avoidEscape": true, "allowTemplateLiterals": true }]
-  }
-}

package/.jshintignore

@@ -1,2 +0,0 @@
-node_modules
-lib/inflection.js

package/.jshintrc

@@ -1,14 +0,0 @@
-{
-  "expr": true,
-  "-W092": false,
-  "quotmark": true,
-  "curly": false,
-  "bitwise": false,
-  "eqeqeq": true,
-  "funcscope": true,
-  "futurehostile": true,
-  "nonew": true,
-  "unused": true,
-  "shadow": true,
-  "loopfunc": true
-}

package/.prettierrc

@@ -1,3 +0,0 @@
-{
-  "singleQuote": true
-}

package/.tern-port

@@ -1 +0,0 @@
-36927

package/.tern-project

@@ -1,7 +0,0 @@
-{
-  "plugins": {
-    "node": {},
-    "lint": {},
-    "node-extension": {}
-  }
-}

package/.travis.yml

@@ -1,47 +0,0 @@
-language: node_js
-
-node_js:
-  - 8
-  - 10
-  - node
-
-notifications:
-  email:
-    recipients:
-      - magic@wizardtales.com
-  webhooks:
-    urls:
-      - https://webhooks.gitter.im/e/509c88551a18006fe93f
-    on_success: change
-    on_failure: always
-    on_start: false
-
-os:
-  - linux
-
-matrix:
-  allow_failures:
-    - node_js: node
-  fast_finish: true
-
-sudo: false
-
-cache:
-  npm: true
-  directories:
-    - node_modules
-
-addons:
-  apt:
-    sources:
-      - ubuntu-toolchain-r-test
-    packages:
-      - g++-4.8
-
-before_install:
-  - export CXX=g++-4.8; export CC=gcc-4.8;
-
-install: npm install
-
-before_script:
-  - cp test/db.config.ci test/db.config.json

package/CODE_OF_CONDUCT.md

@@ -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 dbmigrate@wizardtales.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/

package/CONTRIBUTING.md

@@ -1,81 +0,0 @@
-# Contributing by opening an Issue or Discussing
-
-Whenever you find a bug, which you do not have the time to fix, it is still important
-to get your input. Same goes for feature suggestions and everything else that helps
-a project to get better.
-
-Here are a few points to consider before creating an issue or discussing within one:
-
-1. Make sure you have proper description of your problem or what exactly you want:
-
-We have issue templates in place that should help you with this one and this is really
-important, since we may not just agree with you, if we don't understand your use case.
-
-2. Be constructive and before you post think once more if this is going to waste the maintainers
-   time, or if it is going to actually help them.
-
-Since being constructive, is a big vague, here some simple points that should help you:
-
-2.1. Just stating something is wrong, is not constructive.
-
-When you've got the feeling something is wrong, try to understand first if it is really wrong
-and if it is make suggestions on how to improve, or even better open a PR and make the open source
-world once again even better!
-
-2.2. "Does not work", is not a proper problem description
-
-Neither is, "see title". When you follow the issue template and provide all informations asked for
-you should be pretty fine, in providing us exactly the information we need to help you.
-
-2.3. Follow the CoC and contribute, not attack
-
-An example when you're not contributing, but attacking is, should you just impose you're right
-and you should be followed. It is always about the dialogue, that makes the difference. After all
-you should be fine, by just using your common sense.
-
-# Contributing a Pull Request
-
-Without pull requests from generous people like you, this project
-wouldn't be what it is today. You are planning to contribute aren't you?
-If so, here's a quick guide to creating a great pull request for
-this project:
-
-1. Fork the repo.
-
-2. Copy the test/db.config.example.json to test/db.config.json
-
-3. Run the tests. Pull requests without tests are much less likely to be
-   merged, and it's great to know you're starting with a clean slate: `npm test`.
-   Be sure to check the README for setting up your test databases first.
-
-4. Add a test for your change. Refactoring and documentation changes
-   require no new tests. If you are adding functionality or fixing a bug,
-   please include a test.
-
-5. Make the test pass.
-
-6. Create a commit that complies with our conventions, which you can view
-   [here](https://github.com/conventional-changelog/conventional-changelog/tree/35e60b5be6027fb2784c5103eee111f6f99b045e/packages/conventional-changelog-angular)
-   and last but not least also comply to the [DCO](https://github.com/probot/dco#how-it-works).
-   Which easiest work with just commiting via `git commit -s -m 'your commit message'`.
-
-7. Push to your fork and submit a pull request.
-
-At this point you're waiting on me. In a perfect world I'd commit to
-responding to your request in some short period of time. Unfortunately,
-I'm not able to do that. You'll most likely see me work off several pull
-requests in batches. I may suggest some changes or improvements or alternatives
-at that time. Please don't consider the feedback as a lack of
-appreciation for your time and effort. It most certainly is not.
-
-Some things that will increase the chance that your pull request is accepted,
-are:
-
-* Include good tests
-* Keep the changeset small
-* Stick to existing code conventions
-* Update the documentation, examples elsewhere, guides,
-  whatever is affected by your contribution
-
-See my [pull request etiquette](http://kunkle.org/blog/2013/07/10/pull-request-etiquette/)
-post for more contribution tips.

package/Makefile

@@ -1,8 +0,0 @@
-test:
-	@node node_modules/lab/bin/lab -I verbose,dryRun,SharedArrayBuffer,Atomics,BigUint64Array,BigInt64Array,BigInt,URL,URLSearchParams,TextEncoder,TextDecoder,queueMicrotask --coverage-exclude lib/interface --coverage-exclude lib/transitions
-test-cov:
-	@node node_modules/lab/bin/lab -t 66 -I verbose,dryRun,SharedArrayBuffer,Atomics,BigUint64Array,BigInt64Array,BigInt,URL,URLSearchParams,TextEncoder,TextDecoder,queueMicrotask --coverage-exclude lib/interface --coverage-exclude lib/transitions
-test-cov-html:
-	@node node_modules/lab/bin/lab -r html -o coverage.html -I verbose,dryRun,SharedArrayBuffer,Atomics,BigUint64Array,BigInt64Array,BigInt,URL,URLSearchParams,TextEncoder,TextDecoder,queueMicrotask --coverage-exclude lib/interface --coverage-exclude lib/transitions
-
-.PHONY: test test-cov test-cov-html

package/commitlint.config.js

@@ -1 +0,0 @@
-module.exports = { extends: ['@commitlint/config-angular'] };