actions / actions/toolkit

No "exports" main defined in @actions/core/package.json @v3

Open
#2,294 5 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
5.9k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
Error when building any code using @v3.
No "exports" main defined in @actions/core/package.json

To Reproduce
Try to build this code:

import { setOutput } from '@actions/core';
setOutput('x', 1);

Expected behavior
Code should build as normal.

Screenshots
n/a

Desktop (please complete the following information):

  • OS: [e.g. iOS] linux
  • Browser [e.g. chrome, safari] n/a
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with @actions/core/package.json and the import shown in the reproduction, then run that example through the repository's build process to observe the exports error. Compare the package metadata with the expected entry point. Done means code importing @actions/core builds normally under v3.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.