Closed fetis closed 5 years ago
From the README:
At present, if you want to install packages using ds, you can run ds build in a directory with a Package.toml. This will produce a ds/node_modules directory, which you can move into place by hand. This is a temporary situation!
This works as expected (for now!)
What's the problem to put it directly to the node_modules
? If I want to fix this behavior...
Since this is still very beta I think there is some worry about hosing a working installation, especially given issues like #266 exist.
I'm gonna close this in lieu of a conversation about what "not being in beta" means on the discourse! (Please feel free to re-open if this doesn't solve your needs!)
Is this a feature request or a bug?
it seems bug for me
Expected behavior:
put packages into
node_modules
Actual behavior:
packages are in
ds/node_modules
Steps to replicate:
so, I have fresh master and I did
npm link
incli
folder to installds
globally.I have next Package.toml
I run
ds build
. The package is installed but intods
subfolderSo node module resolution is broken
const figgy = require('figgy-pudding');
Environment info (where relevant)
node -v
): v12.3.1ds --version
): master ca58c5e9e4a94873577e7ce2ee7745d4d540f867Is it expected behavior or a bug?
P.S. I tried the same with an older version from
install.sh
script -- same result.