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
Adds much better support for the unstable Deno workspaces as well as
support for npm workspaces. npm workspaces is still lacking in that we
only install packages into the root node_modules folder. We'll make it
smarter over time in order for it to figure out when to add node_modules
folders within packages.
This includes a breaking change in config file resolution where we stop
searching for config files on the first found package.json unless it's
in a workspace. For the previous behaviour, the root deno.json needs to
be updated to be a workspace by adding `"workspace":
["./path-to-pkg-json-folder-goes-here"]`. See details in
denoland/deno_config#66Closesdenoland#24340Closesdenoland#24159Closesdenoland#24161Closesdenoland#22020Closesdenoland#18546Closesdenoland#16106Closesdenoland#24160
example in shell (shell is
busybox sh
, I added extra newlines around commands to make it easier to read):You can see that there is
file:///tmp/path/to/javascript/app.js
in last 2 lines ofstrings app | grep path/to/javascript
.Is there
deno compile
option to not include.js
file's absolute path in compiled executable?The text was updated successfully, but these errors were encountered: