Skip to content

[tools/avatar-platform] feat: initialize project structure#1

Open
OlegMakarenko wants to merge 10 commits intodevfrom
avatar-platform/init-rebased
Open

[tools/avatar-platform] feat: initialize project structure#1
OlegMakarenko wants to merge 10 commits intodevfrom
avatar-platform/init-rebased

Conversation

@OlegMakarenko
Copy link
Contributor

@OlegMakarenko OlegMakarenko commented Nov 1, 2024

Problem

There is currently no setup for the Avatar Platform web application, which will allow design team members to track and manage avatar design requests from other team members.

Solution

  • Setup the initial project structure for the project.
  • Setup Next.js 15 base for the project.
  • Added Tailwind CSS for styling.
  • Integrated the Next UI component library.
  • Configured ESLint.
  • Configured Stylelint.
  • Added Symbol SDK 3.
  • Setup test configuration.

@Wayonb
Copy link
Contributor

Wayonb commented Nov 4, 2024

Is there a reason not to use the latest? 🤔

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 @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm WARN deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@OlegMakarenko
Copy link
Contributor Author

@Wayonb Thanks! I’ve bumped the dependencies and updated the linter configuration to follow the new ESLint 9 requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants