Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ramesh Mavuluri
    @mrrtech
    Warnings below:

    WARNING in Circular dependency detected:
    libs\backend\src\lib\entities\courses.entity.ts -> libs\backend\src\lib\entities\student.entity.ts -> libs\backend\src\lib\entities\courses.entity.ts

    WARNING in Circular dependency detected:
    libs\backend\src\lib\entities\student.entity.ts -> libs\backend\src\lib\entities\courses.entity.ts -> libs\backend\src\lib\entities\student.entity.ts

    Miloš Lapiš
    @mlc-mlapis
    @mrrtech It's a principal problem. You can use a literal form:
    @ManyToOne('Student', 'courses')
students: string[];
    Ramesh Mavuluri
    @mrrtech
    It is working. Thank you.
    I am not seeing any circular dependency warnings..
    Miloš Lapiš
    @mlc-mlapis
    :thumbsup:
    mdagit
    @mdagit
    i have created and checked in.a project using nx monorepo. node_modules is of course not under source control. what instructions do i need to give other developers who have only a basic node installed (and nothing else) and have just done a fresh "git pull"?
    Miloš Lapiš
    @mlc-mlapis
    npm i
    mdagit
    @mdagit
    @mlc-mlapis so "npm i" will take care of getting them the ng and nx stuff they need as well?
    Miloš Lapiš
    @mlc-mlapis
    @mdagit There is a default project defined in angular.json -> "defaultProject": "myapp". For it, it's enough to run nx serve or ng serve -> both lead to the full command syntax of nx run myapp:serve.
    @mdagit For all other apps, the command has to contain an app name, like nx serve anyapp -> nx run anyapp:serve or so.
    Ramesh Mavuluri
    @mrrtech
    Pls install ng and nx globally. Npm i -g @angular/cli nx
    Joost van Doremalen
    @doender
    I've got several publishable libraries in an Nx monorepo. The dependencies of these libraries are all automatically configured as peer dependencies. Is it possible to change this, as I don't want consumers of my lib to have to install (all) these dependencies by themselves.
    Joshua Reilly
    @jreilly-lukava
    I just create a nestjs application, but when I run it, I get an error, "Cannot find module 'source-map-support/register'"
    Any suggestions?
    Joshua Reilly
    @jreilly-lukava
    hmm, installed source-map-support and everything worked, something is missing a dep someplace I think.
    Luca
    @duvet86
    Hello everybody, I am trying to connect my workspace to nx cloud but when I run nx g @nrwl/nx-cloud:init the console hangs indefinitely.
    Rupesh Tiwari
    @rupeshtiwari
    How to build all apps?
    nx affected:build this only runs when there is changes. I want to create a build for all of my application what is the script for that ?
    Miloš Lapiš
    @mlc-mlapis
    @rupeshtiwari nx run-many --all --target=test --parallel where target you set as you want.
    Rupesh Tiwari
    @rupeshtiwari
    I want to build the applications: can I do something like this ? nx run-many --all --target=apps --parallel
    we have apps, libs and tests so how to build all the applications?
    Rupesh Tiwari
    @rupeshtiwari
    Thanks @mlc-mlapis now I get what exactly you were saying. So I can build entire app and libraries using this script now thanks: nx run-many --all --parallel --target=build
    zwarag
    @zwarag
    When I do ng g c clicker will nx actually map this automatically to nx g c @nrwl/angular:component clicker?
    Ramesh Mavuluri
    @mrrtech
    image.png
    I want to run frontend and backend projects with one npm script is it possible?
    If I want to run 'npm run back-front-start' I am not able to bacuse here the problem is , need to open two terminals. is there any way?
    I have attached my sample scripts - FYI
    Miloš Lapiš
    @mlc-mlapis
    @mrrtech :point_up: January 5, 2021 7:21 PM
    Rupesh Tiwari
    @rupeshtiwari
    how to trigger the build in azure pipeline based on the affected applications. Suppose I have 2 applications and app1 is only changed then how to trigger the build which will create artifacts for that app only ? So that we can release the only single app. If both applications are modified then we need to trigger 2 builds for each applications and release them is there any guideline on this ?
    Matthew Baumgartner
    @mbaumgartner_twitter

    Hi Everyone!
    Perhaps I'm missing something fundamental, however I can't seem to create a production build of Storybook.
    I'm using Angular and Storybook builds fine in development mode using nx run fe-app01:build-storybook

    Has anyone had experience with this, please?

    Dinko Pavicic
    @dinko_nw_twitter
    Hi to eveyone!
    A quick question.. I have to projects, both written in typescript; one is in Nx monorepo and other one in some legacy wannabe 'monorepo' setup with sim-linked modules and other horrific ducktaping.
    We want slowly to tranistion to Nx completely and working on all new code in Nx. While in this transition we also must provide that new code as Typescript libs as 'normal' NPM packages to be used in legacy repo.
    So.. Is it possible to build publishable Typescript library without actually compiling it to JS? To 'build' it, all dependencies listed in built package.json etc. but to stay in Typescript?
    Thank you in advance!
    Rupesh Tiwari
    @rupeshtiwari
    Do we know why package.json files are not copying when I do build? Do I need to copy package.json to dist folder manually as a separate script or nx affected:build will copy pacakge.json automatically and i am missing something ?
    Matthew
    @MatthewS2077
    hi... my workspace is using NX 11.0.0... to update to latest (NX 11.1.1) do I first update my global NX and then run NX migration in workspace? so like this.... npm update nx -g and then in my workspace folder nx migrate next ?
    Matthew
    @MatthewS2077
    that worked anyway... update nx globally, then run nx migrate in workspace
    Matthew
    @MatthewS2077
    hmm nx migrate next updated to 11.1.0-beta4 and not 11.1.1 🤔 ... surely 11.1.1 is "next", but i guess not... anyway nx migrate 11.1.1 go me onto the latest version
    Tim
    @timtos

    Hello everyone. I am trying to migrate a bigger project to nx. And it actually is working using npx create-nx-workspace --preset=angular - except for the unit tests. Currently we are using karma instead of jest. So I thought, I'll do it step by step and first start using nx with karma. So I made another try with:

    npx create-nx-workspace Name1 --preset=empty
    nx generate @nrwl/angular:app Name2 --unit-test-runner=karma

    And I hoped that this would give me the same output as npx create-nx-workspace --preset=angular" only that it is now using karma instead of jest.

    But unfortunately I have no angular.json now. I read already that in this case I have the nx-cli instead of the angular-cli and that this is the reason for the missing angular.json but I actually want an angular.json and the angular-cli as I want as minimal changes in the migration step as possible. First I want to have the current project up and running with anguular-cli/angular.json and karma.

    How can I do that? How to generate an angular.json? How to activate the angular-cli? Or is there another way to achieve my goal?

    De Giovanni
    @tamyfabius
    Hello everyone, I would like to know if anyone knows how to change the version of the workspace and angular from version 11 to version 9 for example ?
    Rupesh Tiwari
    @rupeshtiwari
    Can we make application as publishable and buildable so that it will copy the package.json after we build our application and we can publish in npm repository ?
    Luis Vargas
    @luisvt
    I'm not sure exactly, but applications are supposed to be not publishable
    Rupesh Tiwari
    @rupeshtiwari
    okay thanks!
    I will try to add manually ng-package.json and make it publishable. in our company locally we publish apps and use in .net project to just as directives.
    I ended up writing one article on dependency constraints wanted to just share if it helps to anyone. https://hackmd.io/@rupeshtiwari/S1De3LsRv
    Rupesh Tiwari
    @rupeshtiwari
    Hi I am using node 10.16.2 and when I run jest test I get error ReferenceError: globalThis is not defined
    What version of node do we need to run jest test in nx monorepo?
    Rupesh Tiwari
    @rupeshtiwari
    Just to update the team when i upgraded my node version to latest v14.15.4 then my jest specs are running fine.
    Alex
    @alx-andru
    Hi everyone!
    Rupesh Tiwari
    @rupeshtiwari
    While debugging JEST in Chrome I am seeing this error any idea what am I missing. node --inspect-brk ./node_modules/nx/bin/nx test customers-users I see the error as Could not load content for file:///C:/Projects/GitHub/nx-repo/myorg/packages/nx/bin/nx.ts (System error: net::ERR_FILE_NOT_FOUND)
    Tim
    @timtos
    @rupeshtiwari It says that the file is not found. Did you double-check that the file nx.ts is really present on your system? Luckily it prints out the path where it is looking.
    Roman Fedoseev
    @HammerSpb
    Hi Everyone! I spent a couple of days trying to figure out how to add support of named imports but I cannot figure out how to change babel config and add "babel-plugin-named-asset-import". Could someone help me and point me in the right direction, please?