v3.0.1

Changed

• The isCrossImportPublicApi now also recognizes ./sliceA/@x/sliceB/index.js as a valid public API for cross-imports

Thanks to @gwbaik9717 for this contribution!

v3.0.0

This release adds support for having several index files, useful in full-stack frameworks that shouldn't mix client and server imports.

Changed

• The isIndex function now recognizes dot-separated strings like index.client.js as valid index files, as long as the part until the first dot is index.

Added

• The getIndexes function, similar to the previously existing getIndex, but now returning Array<File> instead of File | undefined

Removed

• The getIndex function, that would either return a single index file or undefined has been removed in favor of getIndexes

v2.4.0

Added

• New constant in the definitions:

  export const crossReferenceToken = "@x"

v2.3.0

Added

• Two new functions: isIndex and isCrossImportPublicApi. Check out the README for the docs
• A bunch of tests for existing functions to make sure nothing breaks later when no one's watching

v2.2.5

Fixed

• Fixed resolveImport returning Unix path separators / on Windows. Now, OS path separators are respected

v2.2.4

Fixed

• Added support for projects using TypeScript 4 with moduleResolution: "node". TypeScript 5 requires that this should be "node10", but we're not picky.

v2.2.3

Fixed

• Removed a console.log that managed to sneak into the last release

v2.2.2

Fixed

• resolveImport previously wouldn't accept a result of parsing tsconfig.json because some values first need to be converted through their specific enum. Meaning that you can now do this:

const tsCompilerOptions = {
  moduleResolution: "Bundler" as const,  // previously this had to be ts.ModuleResolutionKind.Bundler
  baseUrl: ".",
  paths: {
    "~/*": ["./src/*"],
  },
};

resolveImport(
  "~/shared/ui",
  "src/pages/home/ui/HomePage.tsx",
  tsCompilerOptions,
  fs.fileExists,
);

Which is a lot easier! Shame on the API of TypeScript for requiring such hacks, but what can you do /shrug.

v2.2.1

Fixed

• TypeScript was referenced incorrectly, as described in this issue: microsoft/TypeScript#54018

v2.2.0

Added

1. Definitions layerSequence, unslicedLayers, and conventionalSegmentNames to semantically describe FSD rules and keep a single source of truth
2. The isSlice function is now exported, it determines if a folder is a slice based on whether it contains any conventional (or other, configurable) segments

Changed

1. The getAllSlices function now augments the slice object with the layerName property, which is the name of the layer the slice is in.