innermind

Overview

NPM Package Mangement

ESLint

Why is import/no-unresolved disabled?

Two reasons:

1. It requires additional configuration, which may be different for monorepo's, webpack usage, etc.
2. The rule offers little value in a TypeScript world, as the TypeScript compiler will catch these errors.

If you would like to enable this rule, then:

• Enable the rule within your config: 'import/no-unresolved': 'error'
• Install and configure the TypeScript import resolver: eslint-import-resolver-typescript

Mono-Repository Information

Install package dependency

# Initialize Package
npm init --scope @innermindco --workspace ./packages/<package_name>

# Build package
npm run build --workspace ./packages/<package_name>

# Install Internal Packages
npm install @innermindco/server ./packages/<package_name> --save

# Install External Package
npm install package_name --workspace ./packages/server --save

# Install Internal Package to root ./src
npm install @innermindco/server @innermindco/<package_name> --save

# building the monorepo and all its packages
npm run build

# running the compiled index.js
node dist/main.js

References

1. TypeScript Event Sourcing