-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(js): generate ts standalone project with better import path #18197
fix(js): generate ts standalone project with better import path #18197
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
da2c0ea
to
0e0b330
Compare
d712335
to
326f5d4
Compare
326f5d4
to
7489074
Compare
@@ -79,7 +79,7 @@ describe('Storybook generators and executors for standalone workspaces - using R | |||
writeFileSync( | |||
tmpProjPath(`src/app/test-button.tsx`), | |||
` | |||
import { MyLib } from '@${appName}/my-lib'; | |||
import { MyLib } from 'my-lib'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the standalone app isn't scoped by default now (just the app's name in package.json
), the library does not default to a scope either.
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
This PR fixes an issue with standalone TS projects (
npx create-nx-workspace --preset=ts-standalone
) where thename
inpackage.json
is invalid.Current Behavior
The name is something like
@acme/.
Expected Behavior
The name should be the name of the folder (e.g.
acme
).Related Issue(s)
Fixes #