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
Can anybody clarify to me if this is the correct behaviour from nx 16 onwards:
Shutdown any running application if nx detects changes on package.json.
Changes made on buildable libraries and consumed by running applications are not propagated. As in, we MUST re-build the library because applications now consume buildable libraries from the "dist" folder.
If so, the application isn't shutting down correctly. Apparently the node process keeps hanging on (checked with lsof -i:3000). Second, HMR behaviour not being applied to buildable libraries means we have to yarn nx build my-lib every time we make changes on a buildable library.
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
-
Can anybody clarify to me if this is the correct behaviour from
nx
16 onwards:nx
detects changes onpackage.json
.If so, the application isn't shutting down correctly. Apparently the node process keeps hanging on (checked with
lsof -i:3000
). Second, HMR behaviour not being applied to buildable libraries means we have toyarn nx build my-lib
every time we make changes on a buildable library.Beta Was this translation helpful? Give feedback.
All reactions