graphql-boilerplates/graphql-boilerplate-install

graphql-boilerplate-install's Issues

update gc dep to latest beta

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

How can I test local changes to the install flow?

For example, right now I want to add a new folder: string parameter to the deploy command, for the react-fullstack-graphql-basic boilerplate:

- export async function deploy(silent: boolean) {
+ export async function deploy(silent: boolean, folder = '') {
  const options = { stdio: silent ? 'pipe' : 'inherit' }

- return spawn('graphcool', [`deploy`], options)
+ return spawn('graphcool', [`deploy ${folder}`], options)
    .then(res => {
      if (!silent) {
        console.log(res)
      }
    })
    .catch(err => console.error(err))
}

but before pushing I'd like to actually test that this does what I want 🙂

I know that I can use yarn link usually, but I typically invoke this install flow using graphql create, which doesn't use my local dependency 🤔

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:angularmaterial). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

writeEnv: add append option

Currently, writeEnv overwrites the file content of .env. An append option would be super useful to support existing .env files.

For example, in the node-advanced boilerplate, I use env var APP_SECRET that is gone after running writeEnv.

New install flow for boilerplates

With Prisma 1.7, the install flow for boilerplates needs to be updated. Here's what it should look like on a high level:

1. graphql create myapp -b typescript-basic
2. GraphQL CLI downloads the code from the repo
3. GraphQL CLI invokes prisma deploy and specifies the following values for the endpoint:
   • service name: myapp (as provided through graphql create)
   • stage: dev
   • Prisma server: use a sandbox - to ensure best performance ping both eu1 and us1 a few times and calculate average to decide which one is faster, then choose that one.

Fails when env var DEBUG set

Fail to runPing behind proxy

$ graphql create my-app --boilerplate vue-fullstack-basic
[graphql create] Downloading boilerplate from https://github.com/graphql-boilerplates/vue-fullstack-graphql/archive/master.zip...
...
[graphql create] Running boilerplate install script... 
✖ 
request to http://dynamodb.eu-west-1.amazonaws.com/ping?x=5vodv failed, reason: connect ETIMEDOUT 52.94.25.156:80

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency @types/node to v20
• chore(deps): update dependency rimraf to v5
• chore(deps): update dependency typescript to v5
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency @types/node to v8.10.66
• chore(deps): update dependency prisma to v1.34.12
• chore(deps): update dependency rimraf to v2.7.1
• chore(deps): update dependency typescript to v2.9.2
• fix(deps): update dependency cross-spawn to v7
• fix(deps): update dependency node-fetch to v3
• fix(deps): update dependency npm-run to v5

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency node-fetch to v2.7.0
• chore(deps): update dependency prisma to v5
• chore(deps): update dependency ts-node to v10
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

circleci

.circleci/config.yml

npm

package.json

• cross-spawn 5.1.0
• node-fetch ^2.1.2
• npm-run 4.1.2
• sillyname ^0.1.0
• @types/node 8.5.7
• rimraf 2.6.2
• ts-node 4.1.0
• typescript 2.6.2
• prisma 1.3.2

---

• Check this box to trigger a request for Renovate to run again on this repository