Experiment: @atlassian/atlaspack package unifying everything in one package

[alshdavid]

This is just a little weekend experiment. I created the @atlassian/atlaspack package which combines all of the packages in the repo and distributes them under a single package @atlassian/atlaspack.

One package to rule them all

Usage

import { Atlaspack } from '@atlassian/atlaspack'
import { Resolver } from '@atlassian/atlaspack/plugin'
import { FileSystem } from '@atlassian/atlaspack/fs'
import { Asset } from '@atlassian/atlaspack/types'

// Currently only @atlaspack/core is re-exported on the top level
// I could re-export other packages on the top level too as there are no collisions

import { Atlaspack, Resolver, FileSystem } from '@atlassian/atlaspack'

Try it out

npm install @alshdavid/atlaspack
npx atlaspack build

Motivation

• I was curious to see if there was a better way of managing the upgrade path for consumers
• Perhaps this could lead to a better approach to compiling Atlaspack
• Distribute Atlaspack as a single file executable?

Changes

• Added support to the PackageManager for resolving package.json#import statements docs
• Added the @atlassian/atlaspack package
  • Includes core
  • Includes all configs/plugins/runtimes/bundlers/etc

Building

Requires Node 22+ to build and Node 14+ to run

yarn build-native-release
yarn build
yarn build-ts
yarn build-unified

[changeset-bot]

⚠️ No Changeset found

Latest commit: a20b213

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[alshdavid]

@atlaspack/core and related non-plugin packages have fairly few dependencies however the plugins have many.

I tried to bundle the plugins with rspack so they bring their dependencies with them. That worked well but simply copying them is more direct.