aws-samples / aws-samples/amplify-next-template

Template not working out of the box

Open
#81 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
CSS
Stars
236
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

Hi guys,
can someone provide

## Issue 1: working a package.json and amplify.yml

that's working with next js 15, node 21.5 ? I have too many unresolved dependencies and the pipeline never works.
Thanks

## Issue 2: do we have to put all files into root or can we build it within a folder structure like this:
- project_name/amplify
- project_name/src/app
- project_name/root files
- amplify.yml

### Some more infos:

### Environment
- Node.js Version: v21.5.0
- npm Version: 10.2.4

### Issues
- Several packages are reporting that the current Node.js version (v21.5.0) does not meet their required engine specifications (20 || >=22).

```
npm WARN EBADENGINE Unsupported engine {
package: '@isaacs/brace-expansion@5.0.0',
required: { node: '20 || >=22' },
current: { node: 'v21.5.0', npm: '10.2.4' }
}
npm WARN EBADENGINE Unsupported engine {
package: 'glob@11.0.3',
required: { node: '20 || >=22' },
current: { node: 'v21.5.0', npm: '10.2.4' }
}
npm WARN EBADENGINE Unsupported engine {
package: 'minimatch@10.0.3',
required: { node: '20 || >=22' },
current: { node: 'v21.5.0', npm: '10.2.4' }
}
npm WARN EBADENGINE Unsupported engine {
package: 'jackspeak@4.1.1',
required: { node: '20 || >=22' },
current: { node: 'v21.5.0', npm: '10.2.4' }
}
npm WARN EBADENGINE Unsupported engine {
package: 'minimatch@10.0.1',
required: { node: '20 || >=22' },
current: { node: 'v21.5.0', npm: '10.2.4' }
}
npm WARN EBADENGINE Unsupported engine {
package: 'path-scurry@2.0.0',
required: { node: '20 || >=22' },
current: { node: 'v21.5.0', npm: '10.2.4' }
}
npm WARN EBADENGINE Unsupported engine {
package: 'lru-cache@11.1.0',
required: { node: '20 || >=22' },
current: { node: 'v21.5.0', npm: '10.2.4' }
}
```

### npm WARN deprecated

```
npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated @babel/plugin-proposal-object-rest-spread@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
```

### Graph

```
[AmplifyDataConstructInitializationError] Failed to instantiate data construct

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

https://yarnpkg.com/en/docs/selective-version-resolutions

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.
```

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the repository's package.json and amplify.yml, then reproduce the reported install and pipeline failures with the listed Node.js version. Check the documented project layout and the AmplifyDataConstructInitializationError involving duplicate graphql modules. Done means a supported configuration and folder structure are documented or validated without the reported dependency and pipeline failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, graphql, nextjs, node.js
Domain
build-system, cloud, devops, full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.