Error running npm install in preact dependency.
See original GitHub issueHi,
I’m used to using React but decided to give preact a go, along with the preact material ui components. It seems awesome so far…
When I installed both preact along with the jsx babel transform, things went ok. When I installed preact-material-components as well, and imported a single component directly:
import Button from 'preact-material-components/Button';
preact complained about the lack of the transform-object-rest-spread transform.
I could install this directly in my folder but i’d assume that preact should handle those deps. And declare them in the package.json browserify transform options.
I had to do an npm install within the node_modules/preact folder - but this then failed as at the end of the install the preact build command fails ( as there was a lack of config folder ) as its not included in the default npm install.
So i had to clone the preact repo directly in my node_modules and run install to get things working. Not ideal - but just thought i would ask if this was all expected behaviour! 😃
Cheers,
Jamie
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top GitHub Comments
Hmm - that is funky yeah. The git checkout freaks me out a bit - maybe
cp
it to a dotfile and then back?The only thing I don’t like is the
package.json
is still modified after the code has been published, maybe doing something like:what do you think? unless you don’t mind doing a manual checkout after every publish