New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

@cratis/arc.react

Package Overview
Dependencies
Maintainers
1
Versions
113
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@cratis/arc.react

[![Nuget](https://img.shields.io/nuget/v/Cratis.Arc?logo=nuget)](http://nuget.org/packages/Cratis.Arc) [![NPM](https://img.shields.io/npm/v/@cratis/arc?label=@cratis/arc&logo=npm)](https://www.npmjs.com/package/@cratis/arc)

latest
Source
npmnpm
Version
20.1.5
Version published
Maintainers
1
Created
Source

Cratis Arc

Packages / Deployables

Nuget NPM

Builds

.NET Build JavaScript Build Documentation site

Description

Cratis Arc represents an opinionated approach to building consistent applications based on the concepts behind CQRS. It offers extensions for different frameworks and is built on top of ASP.NET Core. One of the traits of Arc has is the bridging between the backend and the frontend. Arc provides a tool, called ProxyGenerator that generates TypeScript code for recognized artifacts matching the criteria of what is considered a commmand or a query.

Contributing

If you want to jump into building this repository and possibly contributing, please refer to contributing.

Prerequisites

The following are prerequisites to work with this repository.

Central Package Management

This repository leverages Central Package Management, which means that all package versions are managed from a file at the root level called Directory.Packages.props.

In addition there are also Directory.Build.props files for setting up common settings that are applied cross cuttingly.

Root package.json

The package.json found at the root level defines all the workspaces. It is assumed

All developer dependencies are defined in the top level package.json. The reason for this is to be able to provide global scripts for every package to use for easier maintenance.

The package.json found at the top level contains scripts that can then be used in a child project for this to work properly.

In a package, all you need to do is to define the scripts to use the global scripts in the `package.json´ of that project:

{
    "scripts": {
        "prepublish": "yarn g:build",
        "clean": "yarn g:clean",
        "build": "yarn g:build",
        "lint": "yarn g:lint",
        "lint:ci": "yarn g:lint:ci",
        "test": "yarn g:test",
        "ci": "yarn g:ci",
        "up": "yarn g:up"
    }
}

FAQs

Package last updated on 03 Apr 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts