You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I totally understand the general desire to use import aliases, but it would also be great if we could at least opt-out and have components generated via untitledui@latest add use relative imports.
#95 suggested that some version at least supported this accidentally, but as of today it appears that an alias is required for the command to successfully execute.
Proposed solution
Allow the CLI user to skip the What is the import alias for your project? question, resulting in a generated component and related files with relative imports instead of the default @/.
Alternatives considered
Refactor an entire monorepo to use aliased imports
Allow aliased imports, creating a stylistic inconsistency within the codebase
Refactor after component creation to use relative imports, either manually or via codeshift
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Problem or use case
I totally understand the general desire to use import aliases, but it would also be great if we could at least opt-out and have components generated via
untitledui@latest adduse relative imports.#95 suggested that some version at least supported this accidentally, but as of today it appears that an alias is required for the command to successfully execute.
Proposed solution
Allow the CLI user to skip the
What is the import alias for your project?question, resulting in a generated component and related files with relative imports instead of the default@/.Alternatives considered
Examples or mockups
No response
Beta Was this translation helpful? Give feedback.
All reactions