build: bump all deps (#480)

* build: bump all deps

Signed-off-by: David Dal Busco <david.dalbusco@outlook.com>

* chore: fmt

Signed-off-by: David Dal Busco <david.dalbusco@outlook.com>

* 📄 Update LLMs.txt snapshot for PR review

---------

Signed-off-by: David Dal Busco <david.dalbusco@outlook.com>
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Author: peterpeterparker

.llms-snapshots/llms-full.txt

@@ -2307,7 +2307,6 @@ juno dev start
 ```
 
 3.  **Create a Satellite** for local dev:
-    
     *   Visit [http://localhost:5866](http://localhost:5866) and follow the instructions.
     *   Update `src/environments/environment.ts` with your Satellite ID.
 

docs/build/components/datastore-storage.md

@@ -13,7 +13,6 @@ Juno gives you two ways to persist data. Both follow a collections-based archite
 Both Datastore and Storage use a unique identifier per item — but they refer to different things and are used differently.
 
 - **Datastore → `key`**:
-
   - A unique string you assign to each document within a collection.
   - Used to retrieve, update, or delete a specific document.
   - Commonly a UUID (e.g. `crypto.randomUUID()`), a nanoid, or any meaningful string like a slug or user ID.

docs/build/datastore/development.mdx

@@ -202,16 +202,13 @@ const myList = await listDocs({
 The function requires a collection and accepts various optional parameters, including a matcher (a regex applied to the document keys and descriptions), pagination options, and sorting order.
 
 1. **`collection`** (required)
-
    - **Description**: The key of the collection from which documents are to be listed.
    - **Type**: `string`
 
 2. **`filter`** (optional)
-
    - **Description**: An optional object that can be used to provide various parameters to filter documents.
 
    a. **`matcher`** (optional)
-
    - **Description**: An object used to filter documents based on their keys or descriptions using regular expressions.
    - **Type**: `ListMatcher`
 
@@ -255,7 +252,6 @@ The function requires a collection and accepts various optional parameters, incl
      ```
 
      - **matcher**: Specifies the type of timestamp comparison. Can be one of the following:
-
        - **equal**: Matches documents where the timestamp is exactly equal to the specified value.
        - **greaterThan**: Matches documents where the timestamp is greater than the specified value.
        - **lessThan**: Matches documents where the timestamp is less than the specified value.
@@ -265,7 +261,6 @@ The function requires a collection and accepts various optional parameters, incl
      - **timestamps**: Used with the `between` matcher to specify a range of timestamps. The range is inclusive of both the start and end values.
 
    b. **`paginate`** (optional)
-
    - **Description**: An object to control pagination of the results
    - **Type**: `ListPaginate`
 
@@ -280,7 +275,6 @@ The function requires a collection and accepts various optional parameters, incl
      - **limit**: The maximum number of documents to return.
 
    c. **`order`** (optional)
-
    - **Description**: Control the sorting order of the results.
    - **Type**: `ListOrder`
 
@@ -294,7 +288,6 @@ The function requires a collection and accepts various optional parameters, incl
      ```
 
    d. **`owner`** (optional)
-
    - **Description**: The owner of the documents.
    - **Type**: `ListOwner`
 

docs/build/storage/development.mdx

@@ -139,16 +139,13 @@ The function requires a collection and accepts various optional parameters, incl
 :::
 
 1. **`collection`** (required)
-
    - **Description**: The key of the collection from which assets are to be listed.
    - **Type**: `string`
 
 2. **`filter`** (optional)
-
    - **Description**: An optional object that can be used to provide various parameters to filter assets.
 
    a. **`matcher`** (optional)
-
    - **Description**: An object used to filter assets based on their keys (fullPaths) or descriptions using regular expressions.
    - **Type**: `ListMatcher`
 
@@ -192,7 +189,6 @@ The function requires a collection and accepts various optional parameters, incl
      ```
 
      - **matcher**: Specifies the type of timestamp comparison. Can be one of the following:
-
        - **equal**: Matches assets where the timestamp is exactly equal to the specified value.
        - **greaterThan**: Matches assets where the timestamp is greater than the specified value.
        - **lessThan**: Matches assets where the timestamp is less than the specified value.
@@ -202,7 +198,6 @@ The function requires a collection and accepts various optional parameters, incl
      - **timestamps**: Used with the `between` matcher to specify a range of timestamps. The range is inclusive of both the start and end values.
 
    b. **`paginate`** (optional)
-
    - **Description**: An object to control pagination of the results
    - **Type**: `ListPaginate`
 
@@ -217,7 +212,6 @@ The function requires a collection and accepts various optional parameters, incl
      - **limit**: The maximum number of assets to return.
 
    c. **`order`** (optional)
-
    - **Description**: Control the sorting order of the results.
    - **Type**: `ListOrder`
 
@@ -231,7 +225,6 @@ The function requires a collection and accepts various optional parameters, incl
      ```
 
    d. **`owner`** (optional)
-
    - **Description**: The owner of the assets.
    - **Type**: `ListOwner`
 

docs/examples/frontend/angular.mdx

@@ -74,7 +74,6 @@ import HowToStart from "../components/how-to-start.mdx";
 <HowToStart />
 
 3. **Create a Satellite** for local dev:
-
    - Visit [http://localhost:5866](http://localhost:5866) and follow the instructions.
    - Update `src/environments/environment.ts` with your Satellite ID.
 

docs/white-paper/architecture.md

@@ -51,7 +51,6 @@ The Console, Observatory, and CDN are the smart contracts which aim to be contro
 In addition to the smart contracts themselves, Juno also provides a variety of libraries, tools and templates. These are meant to be used within the developer workflow when developers start, maintain, and develop their projects. They are designed to provide the best state-of-the-art developer experience.
 
 - **Javascript Libraries**:
-
   - **Core**: The core client library for interacting with satellites.
 
 - **Analytics**: A tracker for integrating analytics.

docs/white-paper/competitors.mdx

@@ -18,9 +18,7 @@ While Juno's blockchain-as-a-service approach offers a unique solution for devel
 ## Comparison
 
 - Web2: Established Platforms (Firebase, Supabase, AppWrite, Vercel, Netlify, Heroku, DigitalOcean, AWS Amplify)
-
   - Advantages:
-
     - **Established**: Well-established platforms with extensive support and resources.
 
     - **Market Share**: Large share of the market with many developers already using these services.
@@ -30,39 +28,32 @@ While Juno's blockchain-as-a-service approach offers a unique solution for devel
     - **Scale**: Proven scalability to handle large workloads efficiently.
 
   - Disadvantages:
-
     - **Stuck in the Web2 Paradigm**: Reliance on centralized infrastructure, lacking the decentralization and security features of Web3 solutions.
 
 <br />
 
 - Web2: Newcomers (Render, Flightcontrol, SST)
-
   - Advantages:
-
     - **Features**: Address market demand for alternatives to established Web2 cloud providers.
 
     - **Scale:** Well-funded and positioned to rapidly gain market share.
 
     - **Trendy**: The “cool kids on the block”.
 
   - Disadvantages:
-
     - **Stuck in the Web2 Paradigm**: Share the same disadvantages as established Web2 providers, including reliance on centralized infrastructure and lack of decentralization and security features inherent in Web3 solutions.
 
 <br />
 
 - Web3: API Platforms (Alchemy, Moralis, thirdweb)
-
   - Advantages:
-
     - **Established**: Strong presence in the Web3 space with robust ecosystems.
 
     - **Market Share**: Large share of the market with many developers already using these services.
 
     - **Cross-Chain Capabilities**: Support for multiple blockchain networks, enhancing interoperability.
 
   - Disadvantages:
-
     - **Focused on Wallets and Transactions**: Primarily centered around wallet management and transactions.
 
     - **Gas Fees**: Transaction costs can be high, impacting the overall cost-efficiency.
@@ -76,15 +67,12 @@ While Juno's blockchain-as-a-service approach offers a unique solution for devel
 <br />
 
 - Web3: Hosting Platforms (Fleek, 4everland)
-
   - Advantages:
-
     - **Established**: Reliable hosting platforms with a focus on Web3 applications.
 
     - **Cross-Chain Capabilities**: Support for multiple blockchain networks, enhancing interoperability.
 
   - Disadvantages:
-
     - **Web2 Auth and DB**: Uses traditional Web2 authentication and database solutions.
 
     - **No DAOs**: Lack of decentralized autonomous organization and governance for their users.
@@ -94,17 +82,14 @@ While Juno's blockchain-as-a-service approach offers a unique solution for devel
 <br />
 
 - Web3: Developer Platforms (Tenderly, OpenZepplin)
-
   - Advantages:
-
     - **Adopted Tooling**: These platforms provide a good developer experience, adopted by many and fulfilling their needs.
 
     - **Infrastructure**: They deliver various tools (Testnets, debuggers, alerting) required for node and smart contract development at scale.
 
     - **Cross-Chain Capabilities**: Support for multiple blockchain networks, enhancing interoperability.
 
   - Disadvantages:
-
     - **Other paradigm**: While both address “Web3 development,” Juno distinguishes itself by focusing on dApp development and could potentially offer bridges.
 
     - **Ease of onboarding**: Web2 developers, particularly those familiar with JavaScript, are more likely to onboard quickly on Juno.