Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add tailwind-eldora-starter example #74184

Open
wants to merge 2 commits into
base: canary
Choose a base branch
from
Open

Add tailwind-eldora-starter example #74184

wants to merge 2 commits into from

Conversation

karthikmudunuri
Copy link

@karthikmudunuri karthikmudunuri commented Dec 20, 2024 •
edited
Loading

title: "Add Tailwind Eldora Starter Example"
author: "karthikmudunuri"
date: "2024-12-20"

Description

This pull request introduces a new example, tailwind-eldora-starter, to the project. This example demonstrates how to integrate Tailwind CSS with Eldora AI for creating UI components via prompts.

Changes Made

  • Added a new folder under examples/ containing the tailwind-eldora-starter setup.
  • Configured Tailwind CSS for styling.
  • Integrated Eldora AI's component library to generate UIs based on user input.
  • Updated the documentation to reference the new example.

Motivation and Context

This example serves as a basic starter template for developers looking to quickly set up a project that utilizes both Tailwind CSS and Eldora AI. It showcases how these tools can be combined to generate dynamic UI components in a highly customizable manner.

How to Test

  1. Clone this repository.
  2. Navigate to the examples/tailwind-eldora-starter directory.
  3. Run npm install to install dependencies.
  4. Run npm run dev to start the development server.
  5. Open the project in your browser at http://localhost:3000 to see the example in action.

Related Issues

  • This pull request addresses issue #XX (if applicable).

Screenshots

Add screenshots or GIFs if applicable to show the new functionality.

Checklist

  • My code follows the code style of this project.
  • I have updated the documentation accordingly.
  • I have tested the changes locally.

@ijjk ijjk added the examples Issue was opened via the examples template. label Dec 20, 2024
@socket-security Socket Security
Copy link

socket-security bot commented Dec 20, 2024 •
edited
Loading

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@codesandbox/sandpack-react@2.19.10 network Transitive: environment, eval +15 71.9 MB danilowoz
npm/@radix-ui/react-avatar@1.1.2 None 0 30.1 kB chancestrickland
npm/@radix-ui/react-icons@1.3.2 None 0 0 B
npm/@radix-ui/react-separator@1.1.1 None 0 13.1 kB chancestrickland
npm/@radix-ui/react-tooltip@1.1.6 None +1 143 kB andy-hook, benoitgrelard, chancestrickland, ...3 more
npm/eslint-config-next@14.2.4 unsafe Transitive: environment, filesystem +13 3.08 MB vercel-release-bot
npm/lucide-react@0.395.0 None 0 23.4 MB ericfennis
npm/next-themes@0.3.0 None 0 18.2 kB paco
npm/next@14.2.4 environment, filesystem, network, shell, unsafe +1 86 MB vercel-release-bot
npm/react-icons@5.4.0 None 0 86.2 MB kamijin_fanta
npm/react-markdown@9.0.1 None +1 54.1 kB wooorm
npm/react-tweet@3.2.1 None 0 89.8 kB lfades
npm/rehype-pretty-code@0.13.2 None +2 63.7 kB atomiks
npm/rehype-stringify@10.0.1 None 0 20.2 kB wooorm
npm/shiki@1.24.3 None +10 12.4 MB antfu, octref, orta, ...1 more
npm/sugar-high@0.7.5 None 0 19.4 kB huozhi

View full report↗︎

@socket-security Socket Security
Copy link

socket-security bot commented Dec 20, 2024 •
edited
Loading

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Possible typosquat attack npm/emoji-regex-xs@1.0.0 ⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/emoji-regex-xs@1.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
examples Issue was opened via the examples template.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@karthikmudunuri @ijjk