Skip to content

Importing a local file without .ts extension causes alchemy cli to be unable to resolve it #623

Description

@Will-Mann-16

I have a pnpm monorepo setup, where I use it's workspace:* package system to link dependencies from all over the repo. Now when those dependencies don't have a .ts on the end of their extension it won't register in the import.

For example, if we setup a quickstart project stack like so

import testEffect from './test'

export default Alchemy.Stack("TestStack", { etc }, Effect.gen(function* () {yield* testEffect }})

It will respond with a Cannot find module "<ROOT_DIR>/test". Is there anyway to resolve this, or do I need to specify all my imports with a .ts extension now - which I'd rather not do?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions