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
our code to detect the installed jsreport dependency works great in normal apps, but when using it inside a monorepo (like npm workspaces) it fails. this is because we just search the jsreport dep in the current cwd, but in a monorepo the deps are installed in different location, we currently have some fallback code that uses normal node.js resolution but i don't remember why we do it just at a specific case, perhaps we just did it to prevent such fallback going to the wider audience because it was not common to have the node_modules somewhere at a higher level (monorepos were not popular before).
we should probably review this and update a bit the logic.
our code to detect the installed jsreport dependency works great in normal apps, but when using it inside a monorepo (like npm workspaces) it fails. this is because we just search the jsreport dep in the current cwd, but in a monorepo the deps are installed in different location, we currently have some fallback code that uses normal node.js resolution but i don't remember why we do it just at a specific case, perhaps we just did it to prevent such fallback going to the wider audience because it was not common to have the node_modules somewhere at a higher level (monorepos were not popular before).
we should probably review this and update a bit the logic.
context: https://forum.jsreport.net/topic/2601/error-when-run-jsreport-start/3
The text was updated successfully, but these errors were encountered: