Qovery Web Console 🌎

Overview


Qovery console

Quick start

yarn
// start project
yarn start
// start storybook
yarn run storybook

Generate an application

Run nx g @nrwl/react:app my-app to generate an application.

You can use any of the plugins above to generate applications as well.

When using Nx, you can create multiple applications and libraries in the same workspace.

Generate a library

Run nx g @nrwl/react:lib my-lib to generate a library.

You can also use any of the plugins above to generate libraries as well.

Libraries are shareable across libraries and applications. They can be imported from @q-frontend/mylib.

Development server

Run nx serve my-app for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run nx g @nrwl/react:component my-component --project=my-app to generate a new component.

Build

Run nx build my-app to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run nx test my-app to execute the unit tests via Jest.

Run nx affected:test to execute the unit tests affected by a change.

Running end-to-end tests

Run ng e2e my-app to execute the end-to-end tests via Cypress.

Run nx affected:e2e to execute the end-to-end tests affected by a change.

Understand your workspace

Run nx dep-graph to see a diagram of the dependencies of your projects.

Further help

Visit the Nx Documentation to learn more.

Comments
  • Environment services table

    Environment services table

    What does this PR do?

    > Link to the JIRA ticket

    • Create the environment service table (all services link to an environment)
    • Create Tag commit component with the copy commit id feature
    image

    PR Checklist

    Global

    • [x] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [x] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [x] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [x] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [x] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released on @staging released 
    opened by WilliamTraoreee 8
  • feat(job): deploy other version for jobs and advanced settings

    feat(job): deploy other version for jobs and advanced settings

    What does this PR do?

    • Deploy another version for job with git
    • Deploy another version for job with container
    • Deploy another version for container
    • Advanced Settings

    Link to the JIRA ticket https://qovery.atlassian.net/jira/software/projects/FRT/boards/23?selectedIssue=FRT-626 https://qovery.atlassian.net/jira/software/projects/FRT/boards/23?selectedIssue=FRT-629

    CleanShot 2022-12-29 at 17 36 09@2x

    Put screenshot following the template before => after here


    PR Checklist

    Global

    • [x] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [x] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [ ] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [ ] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [ ] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released 
    opened by bdebon 7
  • Feat(environment-variable): import feature

    Feat(environment-variable): import feature

    What does this PR do?

    Link to the JIRA ticket

    todo:

    • [x] toggle all true false not working on false
    • [x] input select small does not change its value accordingly to the Control. If the field value is set dynamically through setValue the select will not show that
    • [x] make the window scrollable and wider (see with Remi because the modal is a component tricky that I have never put my hand in) (Created a JIRA ticket for that)
    • [x] plugging the store and the actual api
    • [x] dynamic submit button text saying how many override and new
    • [x] design and refactoring of dropdown part
    • [x] when select is valid would be cool to have the same outline has input
    • [x] switching input value for textarea and try to make an okay design for that... (don't know how I'm gonna do yet) – I won't do that because it complexifies a lot everything and it is how it was implemented on v2 and I've never heard any complain about that
    • [x] error message are breaking the design
    • [x] validation rules for each fields
    • [x] warning tooltip on import are glitchy, they pop too low and I don't know why (Created a JIRA ticket for that)
    • [x] unhide all (needs to create an UI store for this purpose only)
    • [x] saying update instead of overwritten because overwrite and override are different concepts...
    • [x] changing the warning check to make the distinction between override (same key / scope below) and overwrite (same key / same scope)
    • [x] Adding the toggle overwrite / or no overwrite
    • [x] reworking tests

    Screenshot of the actual work where I forced a wider a width CleanShot 2022-07-26 at 18 47 12@2x

    opened by bdebon 7
  • Add feedback Breadcrumb

    Add feedback Breadcrumb

    What does this PR do?

    > Link to the JIRA ticket

    • Adding feedback breadcrumb
    • Adding truncate on the MenuItem
    • Adding truncate on the Header component
    Capture d’écran 2022-06-10 à 08 46 20 Capture d’écran 2022-06-10 à 08 46 56

    PR Checklist

    Global

    • [x] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [x] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [x] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [x] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [x] I made sure the code is type-safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released on @staging released 
    opened by RemiBonnet 7
  • chore(deps): bump react-redux from 7.2.6 to 8.0.1

    chore(deps): bump react-redux from 7.2.6 to 8.0.1

    Bumps react-redux from 7.2.6 to 8.0.1.

    Release notes

    Sourced from react-redux's releases.

    v8.0.1

    This release fixes an incorrect internal import of our Subscription type, which was causing TS compilation errors in some user projects. We've also listed @types/react-dom as an optional peerDep. There are no runtime changes in this release.

    What's Changed

    Full Changelog: https://github.com/reduxjs/react-redux/compare/v8.0.0...v8.0.1

    v8.0.0

    This major version release updates useSelector, connect, and <Provider> for compatibility with React 18, rewrites the React-Redux codebase to TypeScript (obsoleting use of @types/react-redux), modernizes build output, and removes the deprecated connectAdvanced API and the pure option for connect.

    npm i react-redux@latest
    

    yarn add react-redux@latest

    Overview, Compatibility, and Migration

    Our public API is still the same ( <Provider>, connect and useSelector/useDispatch), but we've updated the internals to use the new useSyncExternalStore hook from React. React-Redux v8 is still compatible with all versions of React that have hooks (16.8+, 17.x, and 18.x; React Native 0.59+), and should just work out of the box.

    In most cases, it's very likely that the only change you will need to make is bumping the package version to "react-redux": "^8.0".

    If you are using the rarely-used connectAdvanced API, you will need to rewrite your code to avoid that, likely by using the hooks API instead. Similarly, the pure option for connect has been removed.

    If you are using Typescript, React-Redux is now written in TS and includes its own types. You should remove any dependencies on @types/react-redux.

    While not directly tied to React-Redux, note that the recently updated @types/react@18 major version has changed component definitions to remove having children as a prop by default. This causes errors if you have multiple copies of @types/react in your project. To fix this, tell your package manager to resolve @types/react to a single version. Details:

    [React issue #24304: React 18 types broken since release](facebook/react#24304)

    Additionally, please see the React post on How to Ugprade to React 18 for details on how to migrate existing apps to correctly use React 18 and take advantage of its new features.

    Changelog

    React 18 Compatibility

    React-Redux now requires the new useSyncExternalStore API in React 18. By default, it uses the "shim" package which backfills that API in earlier React versions, so React-Redux v8 is compatible with all React versions that have hooks (16.8+, and React Native 0.59+) as its acceptable peer dependencies.

    We'd especially like to thank the React team for their extensive support and cooperation during the useSyncExternalStore development effort. They specifically designed useSyncExternalStore to support the needs and use cases of React-Redux, and we used React-Redux v8 as a testbed for how useSyncExternalStore would behave and what it needed to cover. This in turn helped ensure that useSyncExternalStore would be useful and work correctly for other libraries in the ecosystem as well.

    Our performance benchmarks show parity with React-Redux v7.2.5 for both connect and useSelector, so we do not anticipate any meaningful performance regressions.

    useSyncExternalStore and Bundling

    The useSyncExternalStore shim is imported directly in the main entry point, so it's always included in bundles even if you're using React 18. This adds roughly 600 bytes minified to your bundle size.

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies released on @staging released 
    opened by dependabot[bot] 7
  • fix(text): fix small typos

    fix(text): fix small typos

    What does this PR do?

    I fix small typos from the web ui


    PR Checklist

    Global

    • [ ] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [ ] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [ ] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [ ] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [ ] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released 
    opened by evoxmusic 6
  • Feat/websocket running status FRT-390

    Feat/websocket running status FRT-390

    What does this PR do?

    Adding websocket running status feature to show all the chip with correct color and running status

    > Link to the JIRA ticket

    List of things done and complex due to the way these websockets work:

    • Matching small id (eg z23oiuio0) and long uuid. Ids of app / database / environment may vary between the websocket message and their id given by the rest API. The rest API will always send our entities with their uuid. In the websocket, sometimes we have a short version of the id and this version begins with a z. We had to create a utility to match the short and long one.
    • Opening one websocket per cluster on an organization. There is no websocket that allows you to get all your environments in a same call. You have to call a websocket per cluster and then save the different env / application and databases in your store
    • Websockets return env, application, database status only if there is a known status for them. If a status becomes STOPPED or Unknown, the status for the app/database/env won't be in the websocket response anymore. Which means that if you had for example a RUNNING status for an app and then suddenly, the status is STOPPED or Unknown, the app won't be in the websocket answer anymore so you can't update it in your store to change the status from Running to Stopped or Unknown. As a result, everytime we have an websocket message, I first force all app/database/env to set their status to null before updating their new value if it is present in the new message. If you don't do this, your app won't be updated at all and will keep the Running Status.
    • Because of the previous point, we had another corner case to handle. When we have different cluster, we have different websockets. If we use the previous point only, each message from each socket will reset the other services and environment. To put simply, if you have an environment on one cluster, if the first websocket set its running status to RUNNING, the next websocket message from the other cluster will reset its running status to null. We have to reset the status only if the services or env belongs to the cluster... That's another tricky check that we have to do on our side
    • Created the interfaces for the websocket answer because the Websocket model is not documented in the api-doc so it's not part of the generated api.
    • Made sure that sockets are closed everytime their are not relevant anymore. In your case, everytime we change orga, we need to close the sockets for the clusters of this past organization.
    • Made sure to auto reconnect the websocket if there is no data in the first answer. The way this websocket works is, if a cluster has nothing to answer, no running status to display, it answers nothing, then the websocket is automatically closed so we have to retry some time to time in case the cluster would have finally something to say
    • Database plugged
    • Made the difference between database managed and contained (managed are not handled by the websocket and we have to use normal status for them)

    todo:

    • Performances issues with useEffect that goes in infinite loop if we do what the linter says
    • Testing the functions that I have put in useCallback

    bugs:

    As opposed to v2 websocket, we tried here to call only at parent level. On the Layout component. The thing is that the socket answer with everything but the data are possibly not yet in the store... So if the message of the socket has passed and there is no new message when we fetch the data, the data will be missing its running status.

    This has been resolved by adding in the websocket component in the useEffect dependency array, the applicationLoadingStatus === 'loaded', dbsLoadingStatus === loaded etc... With that, as soon as we have a loaded status, we replay the useEffect populating, this time, entities that are stored in the slices. Hurray. => Other bug, right now, with the one-to-many relationship, we don't set back the loadingStatus to unloaded. Once we have successfully loaded one collection, the loadingStatus stays forever on loaded... We'll have to address that later.


    PR Checklist

    Global

    • [x] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [ ] I have found someone to review this PR and pinged him

    Store

    • [x] This PR introduces new store changes

    NX

    • [x] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [x] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [x] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released on @staging released 
    opened by bdebon 6
  • Adding Qovery Open-api

    Adding Qovery Open-api

    Adding Qovery Open-api

    Using the package qovery-typescript-axios

    • Update all requests
    • Update all interfaces
    • Update all enums

    PR Checklist

    Global

    • [ ] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labelled as such
    • [ ] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [ ] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [ ] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [ ] I made sure the code is type safe (no any)
    • [ ] I have run the unit tests locally
    • [ ] I have run the e2e tests locally
    • [ ] I have included a feature flag on my feature, if applicable
    released on @staging released 
    opened by RemiBonnet 6
  • fix(create-clone-environment-modal): redirect after request

    fix(create-clone-environment-modal): redirect after request

    What does this PR do?

    • Redirection to the Services page after cloning or creating Environment
    Capture d’écran 2023-01-02 à 09 19 52

    PR Checklist

    Global

    • [x] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [x] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [x] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [x] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [x] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released 
    opened by RemiBonnet 5
  • fix: cluster name visible, missing stop action and git avatar

    fix: cluster name visible, missing stop action and git avatar

    • [x] https://qovery.atlassian.net/jira/software/projects/FRT/boards/23?selectedIssue=FRT-605
    • [x] https://qovery.atlassian.net/jira/software/projects/FRT/boards/23?selectedIssue=FRT-521
    • [x] https://qovery.atlassian.net/jira/software/projects/FRT/boards/23?selectedIssue=FRT-482

    What does this PR do?

    CleanShot 2022-12-28 at 13 00 00@2x

    PR Checklist

    Global

    • [x] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [ ] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [ ] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [ ] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [ ] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released 
    opened by bdebon 5
  • feat(job): overview for jobs

    feat(job): overview for jobs

    What does this PR do?

    • Created a property-card component to display this kind of property card value
    CleanShot 2022-12-27 at 15 17 36@2x
    • Created a JobOverview component to gather everything about job without overloading too much the page-general component
    • Unit testing

    https://qovery.atlassian.net/jira/software/projects/FRT/boards/23?selectedIssue=FRT-624

    CleanShot 2022-12-27 at 15 18 37@2x

    PR Checklist

    Global

    • [ ] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [ ] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [ ] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [ ] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [ ] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    released 
    opened by bdebon 5
  • feat(member): invite member to an organization

    feat(member): invite member to an organization

    What does this PR do?

    > Link to the JIRA ticket

    This PR implements the acceptation flow of an invitation. The development of this feature was highly complexified with a bug with auth0 and getTokenSilently with ignoreCache: true in local only. In Local it works only on chrome (and not on private navigation mode). Does not work locally on firefox / safari / brave.

    This pr still needs some real unit testing and some refinement for the login screen with the invitation message displayed. Design has changed at the last moment.

    CleanShot 2023-01-04 at 18 24 46@2x

    PR Checklist

    Global

    • [x] This PR does not introduce any breaking change
    • [ ] This PR introduces breaking change(s) and has been labeled as such
    • [x] I have found someone to review this PR and pinged him

    Store

    • [ ] This PR introduces new store changes

    NX

    • [ ] I have run the dep-graph locally and made sure the tree was clean i.e no circular dependencies
    • [ ] I have followed the library pattern i.e feature, ui, data, utils

    Clean Code

    • [ ] I made sure the code is type safe (no any)
    • [ ] I have included a feature flag on my feature, if applicable
    opened by bdebon 3
  • chore(deps): bump @nrwl/devkit from 15.0.3 to 15.4.2

    chore(deps): bump @nrwl/devkit from 15.0.3 to 15.4.2

    Bumps @nrwl/devkit from 15.0.3 to 15.4.2.

    Release notes

    Sourced from @​nrwl/devkit's releases.

    15.4.2

    15.4.2 (2022-12-27)

    Bug Fixes

    • bundling: update rollup-plugin-typescript2 to fix typechecking ... (#14020) (95a3bbf)
    • core: adding @​nrwl/vite to packageGroup (d3ef0ea)
    • core: fix the parsing of projects and targets (c3f0cef)
    • js: node executor address already in use (#14023) (4c5a139)
    • testing: change ignoreTestFiles to excludeSpecPattern for cy10+ (#13942) (e91179e)

    Features

    • react: expose setupTailwindGenerator from @​nrwl/react (#14029) (1380ddf)

    15.4.1

    15.4.1 (2022-12-23)

    Bug Fixes

    • core: special case projects for lerna users (f0d67b5)

    15.4.0

    15.4.0 (2022-12-22)

    Bug Fixes

    • angular: cache server build (#13933) (2614669)
    • angular: handle not provided path when generating a component without the project option (#13877) (4e54b1a)
    • angular: missing remotes form mf config should not break mf server (#13901) (dc4a123)
    • angular: support target-less projects in update-15-2-0 (#13755) (9ac9491)
    • bundling: pass --force option to vite dev-server (#13905) (49fa93b)
    • bundling: support custom outExtension for ESM and CJS (e.g. .mjs) (#13985) (98ed2ea)
    • core: additional null check when hashing lockfile (#13803) (efa6ef0)
    • core: consult root package.json when resolving peer deps on package generation (#13949) (f3465a9)
    • core: ensure yarn patch and path versions are correct when pruning (#13847) (03be42e)
    • core: fix lock file pruning multiple versions of dependencies (#13915) (c51c178)
    • core: fix lock file pruning optional dependencies (#13830) (a2adf50)
    • core: fix pruning of pnpm lockfiles with github packages (#13875) (20c4782)
    • core: handle local workspace projects in package.json for affected locator (#13728) (65ecd9c)
    • core: ignore angular.json projects if @​nrwl/angular is not insta… (#13827) (92d33f9)
    • core: local plugins should work on windows (#13801) (75c34c3)
    • core: move generator should work if there are comments in tsconfig #13740 (#13866) (4f98e37)
    • core: reduce likelihood of ENAMETOOLONG error on windows (#13850) (5eabd6c)
    • core: skip npm nested lockfile key mismatch (#13872) (bbfc0fb)
    • devkit: do not move properties when nx.json doesn't exist (#13825) (3fd1841)

    ... (truncated)

    Commits
    • 3fd1841 fix(devkit): do not move properties when nx.json doesn't exist (#13825)
    • 8df1834 feat(react): add nx.server.ready message from Node process to any potential p...
    • 8f7feba fix(devkit): isIncomingVersionGreater should work with prerelease versions (#...
    • 76ee86f feat(core): rename lock file pruning function to createLockFile (#13770)
    • 440112d fix(misc): change ensureDependencies to ensurePackage (#13735)
    • c3bc517 feat(core): prune lock file based on projects dependencies and package.json (...
    • dc1b53a fix(devkit): update missing package message for ensurePackage for cla… (#13665)
    • 61d7d74 fix(misc): fix tsconfig file includes
    • 5b7dba1 fix(react): clean-up after dependency removal from @​nrwl/react (#13563)
    • cded83b feat(react): remove unnecessary dependencies from @​nrwl/react (#13525)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 2
  • chore(deps): bump msw from 0.42.3 to 0.49.2

    chore(deps): bump msw from 0.42.3 to 0.49.2

    Bumps msw from 0.42.3 to 0.49.2.

    Release notes

    Sourced from msw's releases.

    v0.49.2 (2022-12-13)

    Bug Fixes

    v0.49.1 (2022-11-28)

    Bug Fixes

    v0.49.0 (2022-11-19)

    Features

    • support TypeScript 4.9, drop support for TypeScript 4.2, 4.3 (#1467) (af0277da900e20c7fb270ddb46be20deb487aefc) @​wtchnm

    v0.48.3 (2022-11-15)

    Bug Fixes

    v0.48.2 (2022-11-13)

    Bug Fixes

    • resolve absolute worker url against the current path (#1456) (f8d15b41a941613cd4868cf0e85d2d3aa075d067) @​kettanaito

    v0.48.1 (2022-11-10)

    Bug Fixes

    • bufferUtils import path (#1453) (91b2902ded79bea2d649057bd7858862ac91c4c4) @​cksal0805

    v0.48.0 (2022-11-08)

    Features

    v0.47.4 (2022-10-04)

    Bug Fixes

    ... (truncated)

    Commits
    • 7380011 chore(release): v0.49.2
    • 42cdbc7 fix: use globalThis.fetch in ctx.fetch utility (#1490)
    • 37f4f94 chore(deps): bump minimatch from 3.0.4 to 3.1.2 (#1489)
    • af3110e chore(deps): bump decode-uri-component from 0.2.0 to 0.2.2 (#1488)
    • ab8b1ac chore(release): v0.49.1
    • c268796 fix(setupWorker): resolve the TS4094 error (#1477)
    • 2553156 chore(release): v0.49.0
    • af0277d feat: support TypeScript 4.9, drop support for TypeScript 4.2, 4.3 (#1467)
    • e8205e1 chore(release): v0.48.3
    • 7e65e97 fix: reverts beta release
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 2
  • chore(deps-dev): bump eslint-plugin-react from 7.31.8 to 7.31.11

    chore(deps-dev): bump eslint-plugin-react from 7.31.8 to 7.31.11

    Bumps eslint-plugin-react from 7.31.8 to 7.31.11.

    Release notes

    Sourced from eslint-plugin-react's releases.

    v7.31.11

    Fixed

    Changed

    • [Perf] component detection: improve performance by avoiding traversing parents unnecessarily (#3459[] @​golopot)
    • [Docs] [forbid-component-props]: inclusive language w/ allowlist (#3473[] @​AndersDJohnson)
    • [Docs] automate doc generation with eslint-doc-generator (#3469[] @​bmish)

    #1000: jsx-eslint/eslint-plugin-react#1000 #1002: jsx-eslint/eslint-plugin-react#1002 #1005: jsx-eslint/eslint-plugin-react#1005 #100: jsx-eslint/eslint-plugin-react#100 #1010: jsx-eslint/eslint-plugin-react#1010 #1013: jsx-eslint/eslint-plugin-react#1013 #1022: jsx-eslint/eslint-plugin-react#1022 #1029: jsx-eslint/eslint-plugin-react#1029 #102: jsx-eslint/eslint-plugin-react#102 #1034: jsx-eslint/eslint-plugin-react#1034 #1038: jsx-eslint/eslint-plugin-react#1038 #1041: jsx-eslint/eslint-plugin-react#1041 #1043: jsx-eslint/eslint-plugin-react#1043 #1046: jsx-eslint/eslint-plugin-react#1046 #1047: jsx-eslint/eslint-plugin-react#1047 #1050: jsx-eslint/eslint-plugin-react#1050 #1053: jsx-eslint/eslint-plugin-react#1053 #1057: jsx-eslint/eslint-plugin-react#1057 #105: jsx-eslint/eslint-plugin-react#105 #1061: jsx-eslint/eslint-plugin-react#1061 #1062: jsx-eslint/eslint-plugin-react#1062 #1070: jsx-eslint/eslint-plugin-react#1070 #1071: jsx-eslint/eslint-plugin-react#1071 #1073: jsx-eslint/eslint-plugin-react#1073 #1076: jsx-eslint/eslint-plugin-react#1076 #1079: jsx-eslint/eslint-plugin-react#1079 #1088: jsx-eslint/eslint-plugin-react#1088 #1098: jsx-eslint/eslint-plugin-react#1098 #1101: jsx-eslint/eslint-plugin-react#1101 #1103: jsx-eslint/eslint-plugin-react#1103 #110: jsx-eslint/eslint-plugin-react#110 #1116: jsx-eslint/eslint-plugin-react#1116 #1117: jsx-eslint/eslint-plugin-react#1117 #1119: jsx-eslint/eslint-plugin-react#1119 #1121: jsx-eslint/eslint-plugin-react#1121 #1122: jsx-eslint/eslint-plugin-react#1122 #1123: jsx-eslint/eslint-plugin-react#1123 #1130: jsx-eslint/eslint-plugin-react#1130 #1131: jsx-eslint/eslint-plugin-react#1131

    ... (truncated)

    Changelog

    Sourced from eslint-plugin-react's changelog.

    7.31.11 - 2022.11.17

    Fixed

    Changed

    • [Perf] component detection: improve performance by avoiding traversing parents unnecessarily (#3459[] @​golopot)
    • [Docs] forbid-component-props: inclusive language w/ allowlist (#3473[] @​AndersDJohnson)
    • [Docs] automate doc generation with eslint-doc-generator (#3469[] @​bmish)

    #3490: jsx-eslint/eslint-plugin-react#3490 #3484: jsx-eslint/eslint-plugin-react#3484 #3473: jsx-eslint/eslint-plugin-react#3473 #3469: jsx-eslint/eslint-plugin-react#3469 #3464: jsx-eslint/eslint-plugin-react#3464 #3459: jsx-eslint/eslint-plugin-react#3459

    7.31.10 - 2022.10.10

    Fixed

    #3455: jsx-eslint/eslint-plugin-react#3455

    7.31.9 - 2022.10.09

    Fixed

    • [no-unknown-property]: add dialog attributes (#3436[] @​ljharb)
    • [no-arrow-function-lifecycle]: when converting from an arrow, remove the semi and wrapping parens (#3337[] @​ljharb)
    • [jsx-key]: Ignore elements inside React.Children.toArray() (#1591[] @​silvenon)
    • [jsx-no-constructed-context-values]: fix false positive for usage in non-components (#3448[] @​golopot)
    • [static-property-placement]: warn on nonstatic expected-statics (#2581[] @​ljharb)
    • [no-unknown-property]: properly tag-restrict case-insensitive attributes (@​ljharb)
    • [no-unknown-property]: allow webkitDirectory on input, case-insensitive (#3454[] @​ljharb)

    Changed

    #3454: jsx-eslint/eslint-plugin-react#3454 #3451: jsx-eslint/eslint-plugin-react#3451 #3448: jsx-eslint/eslint-plugin-react#3448 #3445: jsx-eslint/eslint-plugin-react#3445 #3444: jsx-eslint/eslint-plugin-react#3444

    ... (truncated)

    Commits
    • 8e5ce6c Update CHANGELOG and bump version
    • 041a120 [Fix] jsx-key: detect keys in logical expression and conditional expression...
    • f5e5da8 [Deps] update array-includes, array.prototype.flatmap, `array.prototype.t...
    • acebf4d [Dev Deps] update @babel/core
    • 4c85b9e [Fix] no-unknown-property: add inert attribute (#3484)
    • 1e16be1 [Docs] automate doc generation with eslint-doc-generator (#3469)
    • 03df592 [actions] rename secret to a more approps name
    • 7a3fd6e [actions] update used actions
    • e40b0a6 [Docs] forbid-component-props: inclusive language w/ allowlist (#3473)
    • a8d2942 [actions] Add npm publish workflow (#3460)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump @reduxjs/toolkit from 1.8.5 to 1.9.1

    chore(deps): bump @reduxjs/toolkit from 1.8.5 to 1.9.1

    Bumps @reduxjs/toolkit from 1.8.5 to 1.9.1.

    Release notes

    Sourced from @​reduxjs/toolkit's releases.

    v1.9.1

    This bugfix release fixes assorted issues that were reported with RTK 1.9.0, and adds a few additional requested tweaks and improvements.

    Changelog

    Fixes

    The createAsyncThunk.withTypes function was fully broken (it type-checked correctly, but pointed to the wrong function due to a name shadowing issue). That now works correctly.

    The maxRetries option for RTKQ was inadvertently filtering out 0 values, and those are now accepted.

    fulfillWithValue had incorrect types that made it appear as if the data was nested an additional level deeper. The types are now correct.

    The ActionCreatorWithoutPayload type was tweaked to force an error when an action creator is accidentally called with an argument, which happens in cases like onClick={todoAdded}. This avoids accidentally passing values like React event objects as the payload.

    Timer handling for batchActions and autoBatchEnhancer now works in more JS runtime environments.

    Other Changes

    The TagDescription type is now exported from RTKQ.

    API endpoints now have a .name field containing the endpoint name, such as "getPokemon".

    Calling promise.abort() on a createAsyncThunk promise before an async condition resolves will now be treated as if the condition itself returned false, bailing out and not dispatching anything.

    The merge option now receives a third argument containing {arg, baseQueryMeta, fulfilledTimeStamp, requestId}, in case that info is useful in deciding how to merge.

    The @reduxjs/rtk-codemods package has been updated to fix cases where the createSliceBuilder codemod didn't preserve fields with function variable arguments, like [todoAdded]: adapter.addOne. That package has been updated to v0.0.3.

    What's Changed

    Full Changelog: https://github.com/reduxjs/redux-toolkit/compare/v1.9.0...v1.9.1

    v1.9.0

    This feature release adds several new options for RTK Query's createApi and fetchBaseQuery APIs, adds a new upsertQueryData util, rewrites RTKQ's internals for improved performance, adds a new autoBatchEnhancer, deprecates the "object" syntax for createReducer and createSlice.extraReducers, deprecates and removes broken utils for getting running query promises, improves TS inference, exports additional types, and fixes a number of reported issues.

    npm i @reduxjs/toolkit@latest
    

    yarn add @​reduxjs/toolkit@​latest </tr></table>

    ... (truncated)

    Commits
    • a87a1ba Release 1.9.1
    • a7ceaa2 Merge pull request #2965 from reduxjs/feature/1.9.1-more-fixes
    • eaf7d5e Pass additional metadata to merge
    • 90ff485 Treat thunk abort signal the same as a false condition result
    • 87bebec Merge pull request #2881 from kyletsang/fix-createslicebuilder-codemod
    • b319c41 Merge pull request #2888 from reduxjs/issues/2886
    • a56a194 Merge pull request #2964 from reduxjs/feature/1.9.1-ts-fixes
    • ce9e05d Expose endpoints.someEndpoint.name field
    • 90283e9 Ensure void action creators can't be passed as event handlers
    • 56ed8a4 Export TagDescription type
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump @radix-ui/react-tooltip from 0.1.7 to 1.0.2

    chore(deps): bump @radix-ui/react-tooltip from 0.1.7 to 1.0.2

    Bumps @radix-ui/react-tooltip from 0.1.7 to 1.0.2.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
Releases(v1.9.0)
Owner
Qovery
Qovery - The simplest way to deploy your apps in the Cloud
Qovery
RWP stands for Roblox web panel, it's a code snippet that you can run via developer console or the provided Google Chrome extension to try out early

RWP stands for Roblox web panel, it's a code snippet that you can run via developer console or the provided Google Chrome extension to try out early Roblox site features before they're officially out without any programming experience.

null 10 Nov 28, 2022
A NodeJS Console Logger with superpowers

LogFlake LogFlake is a NodeJS console logger with superpowers. It has the same API as the usual Console but with beautified output, a message header w

Felippe Regazio 57 Oct 9, 2022
Console log to terminal

Termlog Console log to terminal What it does termlog send the browser console log to your terminal It also comes with a nodejs REPL so you can do some

Quang Ngoc 16 Jan 21, 2022
NpxCard - Write 'npx hariom' in your console.

npx Card This is my NPX card for connecting with me in console or terminal. ❣️ Just Hit npx hariom Will see you in console in just a minute ?? Importa

Hariom gola 2 Jul 26, 2022
Console for mobile browsers

中文 Eruda Console for Mobile Browsers. Demo Browse it on your phone: https://eruda.liriliri.io/ In order to try it for different sites, execute the scr

LiriLiri 13.4k Jan 1, 2023
Another logger in JS. This one offers a console.log-like API and formatting, colored lines and timestamps (or not if desired), all that with 0 dependencies.

hellog Your new logger ! hellog is a general-purpose logging library. It offers a console.log-like API and formatting, extensible type-safety colored

Maxence Lecanu 4 Jan 5, 2022
print faceit elo into the console/chat via telnet

Print MM Ranks and FaceIT elo ingame This tool uses telnet to interact with the console in CS:GO Description Gets faceit elo via the official faceit a

Dominik Wolf 5 Sep 20, 2022
A simple library to draw option menu or other popup inputs and layout on Node.js console.

console-gui-tools A simple library to draw option menu or other popup inputs and layout on Node.js console. console-gui-tools A simple Node.js library

Elia Lazzari 12 Dec 24, 2022
Beautiful errors for Remix, both in browser and console

Rekindled Beautiful errors for Remix, both in browser and console. This project is inspired by php's ignition. I am personally in love with the idea o

FYN Software 22 Nov 22, 2022
A tool to install ubuntu mainline kernels from the console.

Ubuntu Kernel Tool A tool to list, download, and install mainline kernels from the Ubuntu mainline repository. ULTIMATE DISCLAIMER: DO NOT USE THIS TO

Abdullah A. Hassan 9 Jan 21, 2022
The best desktop console calculator yet!

TBCalc - Console Calculator The best desktop console calculator yet! ?? Try TBCalc Online: https://tbcalc.tcb13.com ?? TBCalc Windows App: https://tbc

Tadeu Bento 4 Sep 7, 2022
Quickly create console debugging information for multiple languages.

Debugger for Console Quickly create console debugging information for multiple languages. This plugin uses antfu/starter-vscode as the initial templat

Chestnut 5 Oct 21, 2022
Colorconsole provides an interesting way to display colored info, success, warning and error messages on the developer console in your browser

ColorConsole NPM Package Colorconsole provides an interesting way to display colored info, success, warning and error messages on the developer consol

Hasin Hayder 17 Sep 19, 2022
Personal RasPi console for my car for basic diagnostics and media playback.

mycardashpoc Personal RasPi console for my car for basic diagnostics and media playback. Integrates with OBD and MPD and serves a simple dashboard wit

Anders Evenrud 4 Jul 12, 2022
Base provides advanced Promise Queue Manager, Custom Console Logger and other utilities.

Base Base provides frequently used functionality like cutome logger, response helper, Custom Promise and Instance composer. These are used in almost a

PLG Works 14 Jun 14, 2022
A full query console for Cloudflare's D1 database product.

D1 Console A console/REPL for Cloudflare's D1 Database product. NPM | GitHub Supports all the features expected of a modern database client, including

Isaac McFadyen 59 Dec 23, 2022
Console app - big float calculator <*/+->

Интерпритатор математических выражений Изначально для парсинга математических выражений я реализовал алгоритм сортировочной станции, в текущей версии

Daniil 3 Jul 16, 2022
This is a tool that allows you to join servers on console.

Friend Connect WARNING BEFORE YOU USE THIS TOOL, PLEASE READ THE FOLLOWING: WE AS CONTRIBUTORS ARE NOT RESPONSIBLE FOR ANY DAMAGE OR LOSS CAUSED BY TH

Joshua Carlson 9 Dec 28, 2022
🐈 SDK for Console Cat.

Console Cat SDK Console Cat is a drop-in (cat-themed) telemetry solution for CLIs. We make it easy to track usage so that you can build a better CLI!

Console Cat 5 Jul 24, 2022