Mohammad Kermani
Mohammad Kermani
Tooltips are not provided as a component in Material-UI at this time. So this is postponed to sometime later.
Same happens with `electron-builder`.
I don't know if it's a `electron-builder`, `node-gyp` or repo issue, but it still exists in the latest version of `electron-builder` (`22.11.7` at this time).
It seems a npm bug. I used yarn to install deps and it all works fine.
For me, the solution was to add `repository` to my `package.json`: ```json { "...": "...", "repository": { "type": "git", "url": "" } } ``` Note: It seems `semantic-release-cli` only works...
I don't know if this is going to be merged that soon, but isn't it better if we use the new `exports` field of `package.json` instead of providing `main` field?
I just think it's more modern than the `main` field and nothing more. From [Node docs](https://nodejs.org/api/packages.html#package-entry-points): > For new packages targeting the currently supported versions of Node.js, the "exports"field is...
No. If `peerDependencies` were meant to be copied to `devDependencies` or `dependencies`, they were useless. They have their own use case. They are just _peer_ dependencies.
Still, no, in my humble opinion. 😄 I think you are missing the point of peer dependencies utterly. If you want to test a package containing has some peer dependencies...
I'm still not getting the point. I have seen many (standard) monorepos whose packages don't copy their peer dependencies to dev dependencies. I think it's not correct to ignore them...