UniqueSoft/openpanel
2
0
Fork 0
mirror of https://github.com/stefanpejcic/openpanel synced 2025-06-26 18:28:26 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
Files
4f0d96df10cc0fdace4eccbe6f083ab28a5bc63c
openpanel/packages/devtools/CHANGELOG.md
Stefan Pejcic 09f9f9502d packages
2024-11-07 19:03:37 +01:00

27 KiB
Raw Blame History

@refinedev/devtools

1.2.9

Patch Changes

1.2.8

Patch Changes

1.2.7

Patch Changes

  • #6228 4e375902943c356f269e9f596103fd681ee9afb8 Thanks @aliemir! - refactor(devtools): check both parent and child nodes for representation

    Previously, Refine Devtools's X-Ray feature looked for the representation of the components by looking at the parent nodes until a proper stateNode was found. This was problematic when the parent node was not a proper HTML element. A lack of type checking caused the feature to break in runtime in some cases.

    Adding only a type check for the stateNode is not enough since there may be cases where there are no proper HTML elements in the parent nodes. This change adds a check for the child nodes as well. This way, the feature will look for the representation in both the parent and child nodes.

    First check for a representation node will be done in the child nodes. If a proper representation is not found, an element will be searched in the parent nodes. If a no proper representation is found in the parent nodes, document.body will be used as the representation.

    Resolves #6219

  • #6228 4e375902943c356f269e9f596103fd681ee9afb8 Thanks @aliemir! - fix(devtools): styling issues in the X-Ray feature

    A minimum size was set for the X-Ray feature's overlay to prevent it from being too small.

  • #6185 603c73eb7d376fc2357a577f5921f844a8f444e4 Thanks @aliemir! - feat(devtools): ability to change the port of the devtools server

    Now users can change the port of the devtools server by setting the REFINE_DEVTOOLS_PORT environment variable. Previously, the port was hardcoded to "5001" and could not be changed.

    If you're using @refinedev/cli's runner commands to start your development server, REFINE_DEVTOOLS_PORT will be propagated to your app with appropriate prefix. E.g. if you're using Vite, the environment variable will be VITE_REFINE_DEVTOOLS_PORT and it will be used by the @refinedev/devtools's <DevtoolsProvider /> component to connect to the devtools server.

    • In Next.js apps, it will be prefixed with NEXT_PUBLIC_
    • In Craco and Create React App apps, it will be prefixed with REACT_APP_
    • In Remix apps and other custom setups, the environment variable will be used as is.

    In some scenarios where the environment variables are not passed to the browser, you may need to manually set the Refine Devtools URL in the <DevtoolsProvider /> component via the url prop. Remix apps do not automatically pass environment variables to the browser, so you will need to set the URL manually. If not set, the default URL will be used.

    While the port can be changed, this feature also allows users to host the devtools server on a different machine or domain and provide the <DevtoolsProvider /> with the custom domain URL. This such case will be useful if you're dockerizing your app and devtools server separately.

    Enterprise Edition: Refine Devtools running on ports other than "5001" is only available in the Enterprise Edition. If you're using the Community Edition, Refine Devtools will not work if the port is changed.

    Resolves #5111

  • Updated dependencies [d7fb07e59ddcbef49437c64d3a92b3d47d850225, cbf2fd70a6a0d54722b6541c948ce8cb3f682fb4, c3a75139f82de022b54855e87e200ab38c803af5, 9806a3629256d73bdc18ae808dce217f0108aad2, e2b467528f6a799c3219e3a8fefd4834a0ca0431, 603c73eb7d376fc2357a577f5921f844a8f444e4, 603c73eb7d376fc2357a577f5921f844a8f444e4]:

1.2.6

Patch Changes

1.2.4

Patch Changes

1.2.3

Patch Changes

1.2.2

Patch Changes

1.2.1

Patch Changes

  • #5928 db9756e7908 Thanks @aliemir! - fix: type errors on typescript <5

    Due to the changes in #5881, typescript users below version 5 are facing type errors. This PR fixes the type errors by updating the file extensions required by the d.mts declaration files to provide a compatible declarations for both typescript 4 and 5 users.

  • Updated dependencies [db9756e7908]:

1.2.0

Minor Changes

  • #5898 93c35d82a9c Thanks @aliemir! - feat: devtools selector with all selectables

    Updated devtools selector to display all available elements instead of relying on the user's pointer to select the element.

Patch Changes

1.1.37

Patch Changes

  • #5823 aedc6a2961c Thanks @aliemir! - fix: broken lodash imports in ESM builds

    Fixed lodash imports in ESM builds which requires lodash-es imports to use .js extension to work properly unless the bundler is configured to handle non-fully-specified imports.

    Resolves #5822

  • Updated dependencies [aedc6a2961c]:

1.1.36

Patch Changes

  • #5765 0c197d82393 Thanks @aliemir! - refactor: package bundles and package.json configuration for exports

    Previously, Refine packages had exported ESM and CJS bundles with same .js extension and same types for both with .d.ts extensions. This was causing issues with bundlers and compilers to pick up the wrong files for the wrong environment. Now we're outputting ESM bundles with .mjs extension and CJS bundles with .cjs extension. Also types are now exported with both .d.mts and .d.cts extensions.

    In older versions ESM and CJS outputs of some packages were using wrong imports/requires to dependencies causing errors in some environments. This will be fixed since now we're also enforcing the module type with extensions.

    Above mentioned changes also supported with changes in package.json files of the packages to support the new extensions and types. All Refine packages now include exports fields in their configuration to make sure the correct bundle is picked up by the bundlers and compilers.

  • #5754 56ed144a0f5 Thanks @alicanerdurmaz! - chore: TypeScript upgraded to v5.x.x. #5752

  • Updated dependencies [b20a18e4dfc, 0c197d82393, 51f368eab1a, 33a8a80d80f, 56ed144a0f5, e9bbb1aa5af]:

1.1.35

Patch Changes

1.1.34

Patch Changes

1.1.33

Patch Changes

1.1.32

Patch Changes

1.1.31

Patch Changes

1.1.30

Patch Changes

1.1.29

Patch Changes

1.1.28

Patch Changes

1.1.27

Patch Changes

1.1.26

Patch Changes

1.1.25

Patch Changes

1.1.24

Patch Changes

1.1.23

Patch Changes

1.1.22

Patch Changes

1.1.21

Patch Changes

1.1.20

Patch Changes

1.1.19

Patch Changes

1.1.18

Patch Changes

1.1.17

Patch Changes

1.1.16

Patch Changes

1.1.15

Patch Changes

1.1.14

Patch Changes

  • #5127 4f89ca46ac4 Thanks @aliemir! - Update panel and pin positioning for rounded numbers to avoid subpixel blurry rendering

1.1.13

Patch Changes

  • #5127 4f89ca46ac4 Thanks @aliemir! - Update panel and pin positioning for rounded numbers to avoid subpixel blurry rendering

1.1.12

Patch Changes

1.1.11

Patch Changes

1.1.10

Patch Changes

1.1.9

Patch Changes

1.1.8

Patch Changes

refine devtools

1.0.0

Major Changes

  • #4960 d8e464fa2c4 Thanks @aliemir! - Initial beta release of refine devtools.🎉

    We're releasing refine devtools in beta. refine devtools is designed to help you debug and develop your refine apps. It will be a collection of features including monitoring queries and mutations, testing out inferencer generated codes, adding and updating refine packages from the UI and more. 🤯

    Usage

    Install latest version of @refinedev/cli:

    npm install @refinedev/cli@latest

    🚨 If you don't have @refinedev/cli installed already, you can follow the installation guide to add it to your project.

    Install @refinedev/devtools with @refinedev/cli

    npm run refine devtools init

    devtools-install

    Ta-da! 🎉 Everything is ready now, you can use the refine devtools in your project! 🕶

    Devtools only works in development mode and have no overhead on production builds. You don't need to do anything special to exclude DevTools from your bundle.

Reference in New Issue View Git Blame Copy Permalink