chore(config): remove next.config.ts and update dependencies

[Stivenjs]

This commit deletes the next.config.ts file, which contained configuration for image remote patterns. Additionally, it adds the 'liquidjs' package to both package.json and package-lock.json, updating the project dependencies accordingly.

Summary by CodeRabbit

• New Features

  • Introduced a new data model to support store templates, enabling enhanced template management for stores.

• Enhancements

  • Updated loading messages during the store setup process to provide clearer and more descriptive feedback at each stage.

• Chores

  • Improved image optimization configuration for better clarity.
  • Added the liquidjs package to support template processing.

[coderabbitai]

Walkthrough

A new StoreTemplate data model was introduced with specific fields and authorization rules. The loading messages in the store setup flow were revised for clarity. Next.js image optimization configuration was adjusted by removing empty port properties and adding a clarifying comment. The liquidjs package was added as a dependency.

Changes

File(s)	Change Summary
amplify/data/resource.ts	Added StoreTemplate model with fields, secondary index, and authorization rules.
app/(setup-layout)/first-steps/page.tsx	Updated MultiStepLoader loading messages for the store setup flow.
next.config.js	Removed empty port properties from image optimization config; added explanatory comment.
package.json	Added liquidjs dependency version ^10.21.1.

Poem

In the warren of code, a template appears,
With liquidjs magic to calm any fears.
The loader now sings a new, cheerful tune,
While images optimize beneath a bright moon.
Store templates are ready, so hop in and see—
The setup is smoother for you and for me!
🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

amplify/data/resource.ts (1)

171-186: Well-structured StoreTemplate model with some considerations.

The model structure looks good and aligns with the liquidjs integration. However, consider these improvements:

Considerations for domain uniqueness:

• Multiple stores could potentially have the same domain. Consider if a uniqueness constraint on the domain field is needed.

Template validation suggestions:

• Consider adding validation for templateKey format (e.g., enum or pattern matching)
• The templateData JSON field offers flexibility but consider documenting expected schema or adding runtime validation

These are optional improvements that could enhance data integrity and developer experience.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b49d6f7 and c71a86c.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• amplify/data/resource.ts (1 hunks)
• app/(setup-layout)/first-steps/page.tsx (1 hunks)
• next.config.js (1 hunks)
• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Ejecutar pruebas unitarias
• GitHub Check: Aplicar Prettier
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

next.config.js (1)

3-4: Good documentation improvement.

The added comment clarifies the purpose of the images configuration section, improving code maintainability.

app/(setup-layout)/first-steps/page.tsx (1)

37-40: Well-aligned loading messages with new template engine functionality.

The updated loading messages accurately reflect the new setup steps including template engine configuration, which aligns perfectly with the liquidjs dependency addition and new StoreTemplate model.