Issue in generated tsconfig files for apps & libs
<!-- Please do your best to fill out all of the sections below! --> ## Current Behavior Yesterday, i noticed a strange behavior when working in my newly (!) created nrwl workspace. I develop with the latest `VSCode` (1.52.x) and was not able to "update imports on file move" anymore (i.e., update the import statements when moving a file). This issue #3106 is somewhat related to my problem ## Expected Behavior <!-- What is the behavior that you expect to happen? --> <!-- Is this a regression? .i.e Did this used to be the behavior at one point? --> It should be able to update the import statements. This was able in prior versions of nrwl, but i don't know how many versions we need to go back. ## Steps to Reproduce <!-- Help us help you by making it easy for us to reproduce your issue! --> I did a lot of investigations, but here is what i already found out to (at least for me) successfully reproduce the issue: 1) `npx create-nx-workspace@latest foo` (this should install version 11.1.x) 2) select an `empty` project 3) add a file `a.ts` and `b.ts` to the `apps` folder. Import `b` into `a` and then move `b` to another folder. this should work and the import statements should get properly updated :green_circle: 4) now add a library with `npx nx generate @nrwl/workspace:lib bar` 5) again, create a file `a.ts` and `b.ts` within this newly created lib and import `b` within `a`. Then move `b`, however, the import is not updated :red_circle: 6) this now also fails for the files
Posted by johannesschobel on Jan 12, 2021, 9:31 AM
Tags
Related issues
- I just invented a simple upgrade script for my father's ancient Fedora install.
- Weekly limit is draining like the old 5-hour limit
- Rather people unable to setup a static websites where needed.
- Besides the general awfulness of Windows that you describe, have you looked at C:\Windows recently?
- Does your work involves using teams or ms office or docker?
- Meta: Sorry, no response was returned
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
onboarding (Other)
I just invented a simple upgrade script for my father's ancient Fedora install.
Weekly limit is draining like the old 5-hour limit
Rather people unable to setup a static websites where needed.
Besides the general awfulness of Windows that you describe, have you looked at C:\Windows recently?
Does your work involves using teams or ms office or docker?
Meta: Sorry, no response was returned
Recent FrankerFaceZ Issues with Firefox
Allow creating a `python` shim on `python install`
Issue in generated tsconfig files for apps & libs
<!-- Please do your best to fill out all of the sections below! --> ## Current Behavior Yesterday, i noticed a strange behavior when working in my newly (!) created nrwl workspace. I develop with the latest `VSCode` (1.52.x) and was not able to "update imports on file move" anymore (i.e., update the import statements when moving a file). This issue #3106 is somewhat related to my problem ## Expected Behavior <!-- What is the behavior that you expect to happen? --> <!-- Is this a regression? .i.e Did this used to be the behavior at one point? --> It should be able to update the import statements. This was able in prior versions of nrwl, but i don't know how many versions we need to go back. ## Steps to Reproduce <!-- Help us help you by making it easy for us to reproduce your issue! --> I did a lot of investigations, but here is what i already found out to (at least for me) successfully reproduce the issue: 1) `npx create-nx-workspace@latest foo` (this should install version 11.1.x) 2) select an `empty` project 3) add a file `a.ts` and `b.ts` to the `apps` folder. Import `b` into `a` and then move `b` to another folder. this should work and the import statements should get properly updated :green_circle: 4) now add a library with `npx nx generate @nrwl/workspace:lib bar` 5) again, create a file `a.ts` and `b.ts` within this newly created lib and import `b` within `a`. Then move `b`, however, the import is not updated :red_circle: 6) this now also fails for the files
Comments (0)
No comments yet. Start the discussion.