Zack Sheppard

Make Graphql actually optional

2

The package.json lists the dependency on `@nestjs/graphql` under `optionalDependencies` I think the intention here was to express "if you use graphql, we are compatible with these versions." However, `optionalDependencies` is...

Animation runs repeatedly in interactive mode with loop={false}

5

**Describe the bug** When set to not loop and play the animation once in a block, the expectation I have is that upon entering the block the animation will play...

Is this cocoapod maintained? If so: could we work on making it compatible with the latest OS and Swift versions? If not: could you add a deprecation notice to the...

Superagent deprecation warning

2

Current version of superagent (^5.1.1) is generating a deprecation warning: ``` npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(),...

### Is there an existing issue that is already proposing this? - [X] I have searched the existing issues ### Is your feature request related to a problem? Please describe...

request: ability to define tasks with manifest.yml files

4

## Current State Currently, if a user wants to perform an action like a db migration where you: - Require the roles, privileges, and secrets of the application's main service(s)...

Fix package.json dependency declaration

1

There are two issues with the current structure of the package.json file that cause friction for consumers of this package. 1. The package.json file declares identical `dependencies` and `peerDependencies` objects....

Package should be marked as deprecated and a replacement fork nominated

2

Suggestion: Since the package hasn't been updated since 2019 and has type-breaking incompatibilities with Reacts 17 and 18, it should probably be marked as deprecated and the README updated to...

There are two `@types` packages (react and lodash) in `dependencies`. However, `@types` packages are only used for development and building and shouldn't be included as dependencies. These two packages should...

[Fix] Change type of unused req param to unknown to resolve type conflicts

1

### Description This PR resolves #393 by relaxing the type requirements around the `req` parameter in the callbacks returned by both the `expressJwtSecret` and `passportJwtSecret` integrations. This parameter is not...