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.

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

[Snyk] Upgrade flowbite-react from 0.3.5 to 0.9.0 #232

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tangentdigitalagency
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade flowbite-react from 0.3.5 to 0.9.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 44 versions ahead of your current version.

  • The recommended version was released on 2 months ago.

Release notes
Package name: flowbite-react
  • 0.9.0 - 2024-04-16

    Introducing Drawer and Mega menu

    Summary

    Say hello to Drawer and Mega menu!

    These long-awaited components from the vanilla Flowbite library have finally made their way to Flowbite React. Everything you need to get started - including full theme support, and the full set of examples to match the main Flowbite library - are ready at your fingertips.

    Special thank you to @ dhavalveera for your work on Drawer!

    Changes

    • added Drawer component
    • added Mega menu component
  • 0.8.0 - 2024-04-04

    Minor Changes

    • #1344 bf1bdb0 Thanks @ SutuSebastian! - Rework build process using rollup and tsc

      Summary

      In order to bring more performance to the build process of flowbite-react package, we have to consider transpiling the files using other tools rather than tsc, which is very slow.

      After evaluating various tools including tsup, tshy, and bun build, we chose rollup with the esbuild plugin for transpiling due to its performance and flexibility. We continue to use tsc solely for generating *.d.ts declaration files.

      Changes

      • added rollup + esbuild for transpiling files
        • all files in the cjs directory now have .cjs extension
        • all files in the esm directory now have .mjs extension
        • declaration file types (*.d.ts) have been moved from dist/esm to dist/types
      • changed the build output dir from lib to dist
      • created a facade layer for easier management of the content path as well as the plugin
      • fixed turbo repo dependency tree configs in order for apps/web to properly pipe and require the build output of packages/ui in certain script steps such as build and dev

      Breaking changes

      tailwind.config.js content path:

      old: "node_modules/flowbite-react/lib/esm/**/*.js"

      new: "node_modules/flowbite-react/dist/esm/**/*.mjs" - (flowbite.content() returns it)

      Before

      /** @ type {import('tailwindcss').Config} */
      module.exports = {
        content: [
          // ...
          "node_modules/flowbite-react/lib/esm/**/*.js",
        ],
        plugins: [
          // ...
          require("flowbite/plugin"),
        ],
      };

      After

      const flowbite = require("flowbite-react/tailwind");

      /** @ type {import('tailwindcss').Config} */
      module.exports = {
      content: [
      // ...
      flowbite.content(),
      ],
      plugins: [
      // ...
      flowbite.plugin(),
      ],
      };

      Addresses Issues

      #1326, #1329, #1343

  • 0.7.8 - 2024-04-01

    Patch Changes

  • 0.7.7 - 2024-04-01

    Patch Changes

  • 0.7.6 - 2024-03-29

    What's Changed

    New Contributors

    Full Changelog: https://github.com/themesberg/flowbite-react/compare/v0.7.5...flowbite-react@0.7.6

  • 0.7.5 - 2024-03-20

    What's Changed

    New Contributors

    Full Changelog: v0.7.3...v0.7.5

  • 0.7.4 - 2024-03-20
    No content.
  • 0.7.3 - 2024-03-12

    What's Changed

    New Contributors

    Full Changelog: v0.7.2...v0.7.3

  • 0.7.2 - 2023-12-12
  • 0.7.1 - 2023-12-12
  • 0.7.1-beta - 2023-09-11
  • 0.7.0 - 2023-11-24
  • 0.7.0-beta.6 - 2023-11-26
  • 0.7.0-beta.5 - 2023-11-07
  • 0.7.0-beta.4 - 2023-10-20
  • 0.7.0-beta.3 - 2023-10-11
  • 0.7.0-beta.2 - 2023-10-10
  • 0.7.0-beta.1 - 2023-09-28
  • 0.7.0-beta - 2023-09-11
  • 0.6.4 - 2023-10-03
  • 0.6.3 - 2023-09-30
  • 0.6.2 - 2023-09-29
  • 0.6.1 - 2023-09-23
  • 0.6.1-beta - 2023-09-09
  • 0.6.0 - 2023-09-09
  • 0.6.0-beta - 2023-09-09
  • 0.5.0 - 2023-07-21
  • 0.4.11 - 2023-07-10
  • 0.4.10 - 2023-07-03
  • 0.4.9 - 2023-06-22
  • 0.4.8 - 2023-06-22
  • 0.4.7 - 2023-06-01
  • 0.4.6 - 2023-05-26
  • 0.4.6-beta.1 - 2023-05-26
  • 0.4.6-beta.0 - 2023-05-26
  • 0.4.5 - 2023-05-26
  • 0.4.4 - 2023-04-24
  • 0.4.3 - 2023-04-05
  • 0.4.2 - 2023-03-08
  • 0.4.1 - 2023-03-03
  • 0.4.0 - 2023-03-03
  • 0.3.8 - 2023-01-26
  • 0.3.7 - 2022-12-06
  • 0.3.6 - 2022-12-02
  • 0.3.5 - 2022-11-17
from flowbite-react GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Snyk has automatically assigned this pull request, set who gets assigned.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade flowbite-react from 0.3.5 to 0.9.0.

See this package in npm:
flowbite-react

See this project in Snyk:
https://app.snyk.io/org/tangentdigitalagency/project/1e936b8c-93c4-4677-85e0-0304422164ee?utm_source=github&utm_medium=referral&page=upgrade-pr
@tangentdigitalagency tangentdigitalagency self-assigned this Jun 6, 2024
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