On bootstrapping (using param.macro in its own source) about param.macro HOT 3 CLOSED

Would be interesting to see how others deal with it - I think babel, lerna, jest, rollup & others are bootstrapping their projects.

Actually I had no idea that this was also used here in source files, I had similar problem in other project which lead to my PR here, but I personally need this only for testing purposes - not for the source compilation, so it's generally not a problem for my projects. But I see how this is a problem for this one.

from param.macro.

Babel & lerna can do it because they're in a monorepo structure where a top level package.json contains dependencies that the lower level packages don't but can still access above. I'm not sure that jest tests itself, but the most interesting of those projects was rollup. It literally has a dev dependency on itself which I thought was disallowed.

Apparently, and I can't find this documented anywhere, while npm won't let you explicitly use npm install --save-dev current-package to add that dependency it won't actually do anything to prevent installing it if you just add the dep manually to your package.json and run a bare npm install.

Yarn on the other hand seems perfectly ok with simply adding a project to itself as a dev dependency, or even as a regular dependency with yarn add current-package.

That means it'd be a lot simpler to just have a dev dependency on the last version of param.macro. Guess we've been overcomplicating things 🤦‍♂️.

from param.macro.

Fixed in ddc63e7

The dev experience is already so much better!

from param.macro.