Code Monkey home page Code Monkey logo

parse-server-mysql-adapter's Introduction

MySQL Parse Server Adapter

Build Status codecov.io npm version Greenkeeper badge

This is database adapter to add support of MySQL to Parse Server

Setup

Runs on Parse-Server 2.5.0+ Runs on MySQL >= 5.7.

Create one Database using the MySQL CLI or Query Expression Editor on your MySQL instance.

mysql> CREATE DATABASE `database_here`

Usage

const uri = 'mysql://root@localhost:3306/database_here';
const MySQL = require('parse-server-mysql-adapter').MySQL;
const mysql = new MySQL(uri);

var api = new ParseServer({
  databaseAdapter: mysql.getAdapter(),
  appId: 'myAppId',
  masterKey: 'myMasterKey'
  serverURL: 'http://localhost:1337/parse'
  ...
});

This adapter is backwards compatible with node-mysql. You can pass connection options into the adapter. You can find a list of available options here


Limits in MySQL

Just like other databases MySQL has also some limits that are documented here

Compatibility with Parse Server

Please remember MySQL has recently added a JSON Type in version 5.7. This adapter tried its best to simulate how Parse Server works with other Databases like Postgres, however these features or functions won't work as you expect. Features including JSON and Array will be improved in future updates.

  • Removing From Array : You can only remove strings from array and only one.
  • Regex : Limited support for regex.

Logging

You can enable verbose logging with environment variables:

VERBOSE=1

or

VERBOSE_PARSE_SERVER_MYSQL_ADAPTER=1

parse-server-mysql-adapter's People

Contributors

dplewis avatar greenkeeper[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

parse-server-mysql-adapter's Issues

why

const mysql = new MySQL(uri);
^

TypeError: MySQL is not a constructor
at Object. (G:\desktop\parse\parse.js:8:15)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3

An in-range update of parse is breaking the build 🚨

Version 1.10.1 of parse was just published.

Branch Build failing 🚨
Dependency parse
Current Version 1.10.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

parse is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 7 commits.

  • f713a2c :zap: Release 1.10.1
  • e0ac255 Support React Native < 0.43 once again (#461)
  • ad02823 Fix 477 (#492)
  • 293e2e1 Add Type Polygon to Schema and PolygonContains to query (#455)
  • af28f27 Add methods addAll, addAllUnique and removeAll (#459)
  • 13438fe Addresses flaky test (#458)
  • 2c8cb6f Corrects Guide Link in README.md (#457)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

MySQL is not a constructor

Hello,
thanks for the grat job.
is the project still active?
i'm havin issues using this adapter.
MySQL is not a constructor
details and infos on the screenshot.
can anyone help?
Screenshot from 2022-11-27 21-48-20

An in-range update of lodash is breaking the build 🚨

Version 4.17.5 of lodash was just published.

Branch Build failing 🚨
Dependency lodash
Current Version 4.17.4
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

the code copied didn't work

Hello!
I copy the code to run, but found "MySQL is not a constractor", I change "const MySQL = require('parse-server-mysql-adapter').MySQL" into "const MySQL = require('parse-server-mysql-adapter')", then the code run continue.
After that, I face another problem that request me to add fileAdaptor once I add database adaptor, I add "var FSFilesAdapter = require('@parse/fs-files-adapter');", and this was solved.
Finally, what problem I met is "TypeError: this.adapter.updateSchemaWithIndexes is not a function", so I had no way but turn to you.
Can you run the demo code nowadays and how can I solve this.
Thank you very much!

An in-range update of eslint-config-airbnb-base is breaking the build 🚨

Version 11.3.0 of eslint-config-airbnb-base just got published.

Branch Build failing 🚨
Dependency eslint-config-airbnb-base
Current Version 11.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-airbnb-base is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 4.3.0 of eslint just got published.

Branch Build failing 🚨
Dependency eslint
Current Version 4.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v4.3.0
  • 91dccdf Update: support more options in prefer-destructuring (#8796) (Victor Hom)
  • 3bebcfd Update: Support generator yields in no constant condition (#8762) (Victor Hom)
  • 96df8c9 Fix: Handle fixing objects containing comments (fixes #8484) (#8944) (Brian Schemp)
  • e39d41d Docs: Make peerDependencies package.json snippet valid JSON (#8971) (Sam Adams)
  • a5fd101 Fix: duplicated error message if a crash occurs (fixes #8964) (#8965) (Teddy Katz)
  • f8d122c Docs: trailing commas not allowed in json (#8969) (Scott Fletcher)
  • d09288a Chore: Use output: null to assert that a test case is not autofixed. (#8960) (薛定谔的猫)
  • e639358 Update: add question to confirm downgrade (fixes #8870) (#8911) (Toru Nagashima)
  • 601039d Docs: fix badge in eslint-config-eslint readme (#8954) (Teddy Katz)
  • 3c231fa Update: add enforceInMethodNames to no-underscore-dangle (fixes #7065) (#7234) (Gabriele Petronella)
  • 128591f Update: prefer-numeric-literals warns Number.parseInt (fixes #8913) (#8929) (Kevin Partington)
  • 846f8b1 Docs: Clarified that core PRs require issue in maintainer guide (#8927) (Kevin Partington)
  • 55bc35d Fix: Avoid shell mangling during eslint --init (#8936) (Anders Kaseorg)
  • 10c3d78 Chore: fix misleading indent test (#8925) (Teddy Katz)
  • fb8005d Update: no-restricted-globals custom error messages (fixes #8315) (#8932) (Kevin Partington)
  • a747b6f Chore: make minor improvements to indent internals (#8947) (Teddy Katz)
  • 1ea3723 Update: fix indentation of parenthesized MemberExpressions (fixes #8924) (#8928) (Teddy Katz)
  • 9abc6f7 Update: fix BinaryExpression indentation edge case (fixes #8914) (#8930) (Teddy Katz)
  • 0e90453 Docs: Fixing broken cyclomatic complexity link (fixes #8396) (#8937) (Chris Bargren)
  • a8a8350 Chore: improve performance of indent rule (#8905) (Teddy Katz)
  • 764b2a9 Chore: update header info in indent (#8926) (Teddy Katz)
  • 597c217 Fix: confusing error if plugins from config is not an array (#8888) (Calvin Freitas)
  • 3c1dd6d Docs: add description of no-sync allowAtRootLevel option (fixes #8902) (#8906) (Teddy Katz)
  • 933a9cf Chore: add a fuzzer to detect bugs in core rules (#8422) (Teddy Katz)
  • 45f8cd9 Docs: fix verifyAndFix result property name (#8903) (Tino Vyatkin)
  • 1a89e1c Docs: Fix always-multiline example in multiline-ternary docs (#8904) (Nathan Woltman)
Commits

The new version differs by 28 commits.

  • 2874d75 4.3.0
  • 1c83662 Build: changelog update for 4.3.0
  • 91dccdf Update: support more options in prefer-destructuring (#8796)
  • 3bebcfd Update: Support generator yields in no constant condition (#8762)
  • 96df8c9 Fix: Handle fixing objects containing comments (fixes #8484) (#8944)
  • e39d41d Docs: Make peerDependencies package.json snippet valid JSON (#8971)
  • a5fd101 Fix: duplicated error message if a crash occurs (fixes #8964) (#8965)
  • f8d122c Docs: trailing commas not allowed in json (#8969)
  • d09288a Chore: Use output: null to assert that a test case is not autofixed. (#8960)
  • e639358 Update: add question to confirm downgrade (fixes #8870) (#8911)
  • 601039d Docs: fix badge in eslint-config-eslint readme (#8954)
  • 3c231fa Update: add enforceInMethodNames to no-underscore-dangle (fixes #7065) (#7234)
  • 128591f Update: prefer-numeric-literals warns Number.parseInt (fixes #8913) (#8929)
  • 846f8b1 Docs: Clarified that core PRs require issue in maintainer guide (#8927)
  • 55bc35d Fix: Avoid shell mangling during eslint --init (#8936)

There are 28 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of jasmine-spec-reporter is breaking the build 🚨

Version 4.2.0 of jasmine-spec-reporter just got published.

Branch Build failing 🚨
Dependency jasmine-spec-reporter
Current Version 4.1.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As jasmine-spec-reporter is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v4.2.0

Feature

  • Support reporting errors in afterAll #210, #214
Commits

The new version differs by 36 commits.

  • 68cc0d0 4.2.0
  • a00e167 1.2.0
  • 1375a92 Update CHANGELOG.md
  • 2acc40c Support reporting errors in afterAll.
  • a8af52a chore(lint): remove strict-type-predicates rule
  • 5e1a958 chore(package): update jasmine-core to version 2.7.0
  • 3c281ea chore(yarn.lock): update yarn.lock
  • fd4cbe5 chore(package): update jasmine to version 2.7.0
  • 68448c2 chore(yarn.lock): update yarn.lock
  • a211ce7 chore(package): update codecov to version 2.3.0
  • b300292 chore(yarn.lock): update yarn.lock
  • 6a2e361 chore(package): update @types/node to version 8.0.18
  • c34cb37 chore(yarn.lock): update yarn.lock
  • fdaf887 chore(package): update nyc to version 11.1.0
  • c3c7261 Suggest debugging with console.warn()

There are 36 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 11.1.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.0.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 5 commits.

  • a3f033f chore(release): 11.1.0
  • a076951 chore: upgrade to latest version of istanbul-lib-instrument
  • 8768afe feat: upgrade to version of spawn-wrap that supports .EXE (#626)
  • 2d92501 chore: attempt to fix appveyor (#623)
  • bbadc1f feat: add support for per file coverage checking (#591)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.8.0 of eslint-plugin-import was just published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.7.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 35 commits.

  • 95b1ba6 disable AppVeyor coveralls
  • 4071379 #842/#944 changelog note
  • 8702af7 #744 changelog note
  • 91c5318 #886 / #891 changelog notes
  • 1b3f544 bump v2.8.0
  • cef88f2 Merge pull request #944 from alexgorbatchev/alexgorbatchev/issue-842
  • c246b9e #842 Fixes Cannot read property 'some' of undefined
  • 1958e0b [Tests] fix broken test on master
  • 68f63f5 forgot @k15a's user link 😅
  • 5f5fbf6 changelog notes for #620 + #632
  • 92dd662 Merge pull request #632 from k15a/master
  • 1ba1c3a removing changelog note, will re-add
  • 146f87f changelog notes for #720 + #858
  • 57527c7 Merge pull request #858 from laysent/master
  • 006ddeb Merge remote-tracking branch 'refs/remotes/benmosher/master'

There are 35 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

TypeError: Cannot read property '*' of undefined

image

TypeError: Cannot read property '*' of undefined
    at SchemaData.get (C:\Users\Tian-PC\Downloads\source\node_modules\parse-server\lib\Controllers\SchemaController.js:671:84)
    at SchemaController.enforceClassExists (C:\Users\Tian-PC\Downloads\source\node_modules\parse-server\lib\Controllers\SchemaController.js:1013:24)
    at C:\Users\Tian-PC\Downloads\source\node_modules\parse-server\lib\Controllers\DatabaseController.js:1432:70
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

"dependencies": {
    "@parse/fs-files-adapter": "^1.2.1",
    "express": "^4.17.1",
    "lodash": "^4.17.21",
    "mysql2": "^2.3.2",
    "npmlog": "^5.0.1",
    "parse": "^3.3.1",
    "parse-dashboard": "^3.2.1",
    "parse-server": "^4.10.4"
  }

Cannot Query JsonArrays like "Owner.post"

My problem when I try to do query in a JsonArray I get this message in server console :
Unknown column 'Owner.post' in 'where clause'
is there an alternative to dots "." in queries JsonArray ?
or what In can do to query JsonArray ?

An in-range update of mysql2 is breaking the build 🚨

Version 1.4.0 of mysql2 just got published.

Branch Build failing 🚨
Dependency mysql2
Current Version 1.3.6
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

mysql2 is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 16 commits.

  • 860f504 1.4.0
  • 581304d 1.4.0
  • 101d2c4 1.3.7
  • c22cb56 Merge pull request #622 from tsholmes/fix/prepared_promise_errors
  • 60f193f Fix error handling in promise prepared statement
  • 4b4f68e Add failing test
  • cebd9bd Merge pull request #620 from rhendric/fix/sidorares/node-mysql2#577
  • ddb7df6 redo event delegation in promise wrappers to be lazy, self-cleaning
  • 914c22c Merge pull request #618 from bencebalogh/617-datestrings-ms-precision
  • 674efe0 Read ms in Packet.prototype.readDateTimeString
  • 8cd97ec Merge pull request #615 from sidorares/promise-changeuser
  • e4009ae don't use destructuring assignment, node 4.8 can't handle it
  • 24c7724 lint
  • e1dbc2b fix promise argiments
  • c426924 added testChangeUser

There are 16 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

TypeError: MySQL is not a constructor

(node:18776) UnhandledPromiseRejectionWarning: TypeError: MySQL is not a constructor

I've got this error.

here is my code
`const { MySQL } = require('parse-server-mysql-adapter');

const mysql = new MySQL(DB_URI);

const parseServerAPI = new ParseServer({
databaseURI: mysql.getAdapter(),
cloud: path.resolve(__dirname, 'server/cloud/main.ts'),
appId: APP_ID,
masterKey: MASTER_KEY,
serverURL: SERVER_URL,
appName: APP_NAME,
});`

MariaDB Support

MariaDB is backwards compatible with MySQL except for JSON type. :json is converted to :longtext (string). Plugins exists for support, JSON.parse will also work. Later version could also add support.

Multiple Breaking Errors after upgrading to latest Parse.

TypeError: Cannot read property '*' of undefined at SchemaData.get (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\SchemaController.js:549:84) at SchemaController.getClassLevelPermissions (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\SchemaController.js:1308:27) at SchemaController.validatePermission (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\SchemaController.js:1304:53) at validateClassName.then.then.schemaController (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\DatabaseController.js:796:63) at process._tickCallback (internal/process/next_tick.js:68:7) error: Uncaught internal server error.Cannot read property '*' of undefined {"stack":"TypeError: Cannot read property '*' of undefined\n at SchemaData.get (C:\\apps\\rentoza-stories\\server\\node_modules\\parse-server\\lib\\Controllers\\SchemaController.js:549:84)\n at SchemaController.getClassLevelPermissions (C:\\apps\\rentoza-stories\\server\\node_modules\\parse-server\\lib\\Controllers\\SchemaController.js:1308:27)\n at SchemaController.validatePermission (C:\\apps\\rentoza-stories\\server\\node_modules\\parse-server\\lib\\Controllers\\SchemaController.js:1304:53)\n at validateClassName.then.then.schemaController (C:\\apps\\rentoza-stories\\server\\node_modules\\parse-server\\lib\\Controllers\\DatabaseController.js:796:63)\n at process._tickCallback (internal/process/next_tick.js:68:7)"} TypeError: Cannot read property '*' of undefined at SchemaData.get (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\SchemaController.js:549:84) at SchemaController.getClassLevelPermissions (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\SchemaController.js:1308:27) at SchemaController.validatePermission (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\SchemaController.js:1304:53) at validateClassName.then.then.schemaController (C:\apps\rentoza-stories\server\node_modules\parse-server\lib\Controllers\DatabaseController.js:796:63) at process._tickCallback (internal/process/next_tick.js:68:7)

An in-range update of parse-server is breaking the build 🚨

Version 2.6.0 of parse-server just got published.

Branch Build failing 🚨
Dependency parse-server
Current Version 2.5.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

parse-server is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes 2.6.0

2.6.0

Full Changelog

Breaking Changes:

  • [email protected]: A new deprecation notice is introduced with parse-server-s3-adapter's version 1.2.0. An upcoming release will remove passing key and password arguments. AWS credentials should be set using AWS best practices. See the Deprecation Notice for AWS credentials section of the adapter's README.

New Features

Improvements

  • Postgres: Adds support nested contains and containedIn, thanks to Diamond Lewis
  • Postgres: Adds support for null in containsAll queries, thanks to Diamond Lewis
  • Cloud Code: Request headers are passed to the cloud functions, thanks to miguel-s
  • Push: All push queries now filter only where deviceToken exists

Bug Fixes:

  • Fixes issue affecting updates of _User objects when authData was passed.
  • Push: Pushing to an empty audience should now properly report a failed _PushStatus
  • Linking Users: Fixes issue affecting linking users with sessionToken only

Dependency Updates:

Devevelopment Dependencies Updates:
Commits

The new version differs by 31 commits.

  • 540daa4 :zap: Release 2.6.0 (#4126)
  • 2e1ba66 Fix/user update issue (#4123)
  • a103871 fix some typos. (#4112)
  • f840394 Greenkeeper/parse server s3 adapter 1.2.0 (#4118)
  • da2bfca fix(package): update ws to version 3.1.0 (#4053)
  • 1798c07 fix(package): update mime to version 1.4.0 (#4120)
  • e2d1fd3 fix(package): update semver to version 5.4.0 (#4044)
  • ea67d23 Improvements for sending push performance (#4122)
  • cfd7bc0 chore(package): update uws to version 8.14.1 (#4078)
  • c4d921e chore(package): update jasmine to version 2.8.0 (#4115)
  • 8513b69 chore(package): update bcrypt to version 1.0.3 (#4113)
  • ff4ae55 Fix minor comment typo (#4110)
  • 5d359c3 chore(package): update babel-register to version 6.26.0 (#4097)
  • 6e23822 chore(package): update babel-core to version 6.26.0 (#4096)
  • b45f308 fix(package): update mongodb to version 2.2.31 (#4089)

There are 31 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of codecov is breaking the build 🚨

Version 2.3.0 of codecov just got published.

Branch Build failing 🚨
Dependency codecov
Current Version 2.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As codecov is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-flowtype is breaking the build 🚨

Version 2.35.1 of eslint-plugin-flowtype just got published.

Branch Build failing 🚨
Dependency eslint-plugin-flowtype
Current Version 2.35.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-flowtype is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v2.35.1

<a name"2.35.1">

2.35.1 (2017-09-01)

Bug Fixes

  • Properly check line breaks in space-after-type-colon (#268) (f96ce986)
Commits

The new version differs by 1 commits.

  • f96ce98 fix: Properly check line breaks in space-after-type-colon (#268)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Unable to ensure uniqueness for usernames: Parameter "url" must be a string, not object

hello.

I've got this error when connecting to the database: Unable to ensure uniqueness for usernames: Parameter "url" must be a string, not object

here is my code:
`
const MySQL = require('parse-server-mysql-adapter');

const mysql = new MySQL('mysql://c1439623d_dev:xxxxx@localhost:3306/dev');

const parseServerAPI = new ParseServer({
databaseURI: mysql.getAdapter(),
cloud: path.resolve(__dirname, 'server/cloud/main.ts'),
appId: APP_ID,
masterKey: MASTER_KEY,
serverURL: SERVER_URL,
appName: APP_NAME,
});
`
image

image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.