Dependencies & critical paths

What you configure

analyzeCriticalPath

Supply the task collection to the licensed planner.

durationMinutes / dependencyIds

Describe each task's duration and prerequisite task IDs.

resourceIds

Retain resource context in the analysis result when relevant.

Integration code example

1. Create uniquely identified tasks with valid durations and dependency links.
2. Run the analysis and inspect the deterministic critical path and project duration.
3. Render the results in your own dependency or timeline presentation and recompute after task changes.

Copy this TypeScript into your application, not the browser console. Replace YOUR_WTS_LICENSE_KEY with an entitlement issued for your deployment origin. A WTS license is not a Google, Microsoft or CalDAV credential. These examples are documentation only and never execute on this page.

npm install @wts-calendar/core

import { verifyCalendarLicense } from '@wts-calendar/core';
import { AdvancedResourcePlanner } from '@wts-calendar/core/advanced-resource-planning';

const license = await verifyCalendarLicense('YOUR_WTS_LICENSE_KEY');
const planner = new AdvancedResourcePlanner({
  license,
  timeZone: 'UTC',
  resources: [
    { id: 'design', title: 'Design studio', capacity: 2 },
    { id: 'engineering', title: 'Engineering', capacity: 4 },
  ],
  events: [
    {
      id: 'review',
      title: 'Design review',
      resourceId: 'design',
      start: '2026-09-07T09:00:00Z',
      end: '2026-09-07T10:30:00Z',
    },
  ],
});

export const analysis = planner.analyzeCriticalPath([
  { id: 'design', durationMinutes: 90 },
  {
    id: 'build',
    durationMinutes: 180,
    dependencyIds: ['design'],
    resourceIds: ['engineering'],
  },
  { id: 'inspect', durationMinutes: 45, dependencyIds: ['build'] },
  { id: 'notes', durationMinutes: 30, dependencyIds: ['design'] },
]);
console.table(analysis.tasks);
console.log(analysis.criticalPathIds, analysis.projectDurationMinutes);

Application responsibilities

The engine returns data, not a built-in chart. Render results in your application and call planner.setData() after resources, events or profiles change.

Map returned critical indicators into your own timeline rendering. Dependency analysis does not automatically schedule calendar events or level resource capacity.

Behavior and lifecycle

• The result includes one deterministic critical path and per-task float information.
• Cycles, unknown dependencies, duplicate IDs, and invalid durations fail before a result is returned.