JSPM

@nx-dotnet/core

3.0.2
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 24517
  • Score
    100M100P100Q152224F
  • License MIT

Package Exports

  • @nx-dotnet/core
  • @nx-dotnet/core/src/generators/app/generator
  • @nx-dotnet/core/src/generators/app/generator.js
  • @nx-dotnet/core/src/generators/nuget-reference/generator
  • @nx-dotnet/core/src/generators/nuget-reference/generator.js
  • @nx-dotnet/core/src/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@nx-dotnet/core) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Prerequisites

Installation

NPM

npm i --save-dev @nx-dotnet/core
npx nx g @nx-dotnet/core:init

PNPM

pnpm i --save-dev @nx-dotnet/core
pnpx nx g @nx-dotnet/core:init

Yarn

yarn add --dev @nx-dotnet/core
npx nx g @nx-dotnet/core:init

Generate and run your first api!

Generate my-api, and my-api-test with C# and nunit tests.

npx nx g @nx-dotnet/core:app my-api --test-template nunit --language C#

Run my-api locally

npx nx serve my-api

nrwl/nx/enforce-module-boundaries support

Nrwl publishes an eslint rule for enforcing module boundaries based on tags in a library. We recently added similar support to nx-dotnet.

To avoid duplicating the rules configuration, if your workspace already has it, nx-dotnet can read the dependency constraints from your workspace's eslint files. It does this by looking at what is configured for typescript files.

If your workspace does not currently contain eslint, do not worry! You do not have to install eslint just for its configuration. The same dependency constraints can be placed inside of your .nx-dotnet.rc.json file at workspace root. This should look something like below:

{
  "moduleBoundaries": [
    {
      "onlyDependOnLibsWithTags": ["a", "shared"],
      "sourceTag": "a"
    },
    {
      "onlyDependOnLibsWithTags": ["b", "shared"],
      "sourceTag": "b"
    },
    {
      "onlyDependOnLibsWithTags": ["shared"],
      "sourceTag": "shared"
    }
  ],
  "nugetPackages": {}
}