Open wolfson-rebel opened 4 years ago
Same issue here. Haven't found a workaround
I have the same. I was looking into it and it looks like the contents of the package on npm are broken.
It's trying to execute prepack.prepack on content parameter of the extract function. It doesn't really make sense, so I'm assuming the problem is in publishing the latest codebase to npm.
@alinaish or @Ffloriel would you be able to publish version 1.0.0 (the current codebase that is using esprima) to npm? I would hate to have to clone this and publish under different name without any significant contribution.
Yep, prepack was used on the previous version. The current codebase was not published. Will do now, thanks for the ping
Awesome, thank you!
Does this work for anyone? I am still seeing an empty object for the default export/import.
> var p = require('purgecss-from-js')
undefined
> p
{}
> typeof p
'object'
> Object.entries(p)
[]
When I go back to the old (v0.1.0) release I see a function like I expect:
> require('purgecss-from-js')
[Function: PurgeFromJs]
Sorry, I'm just using a modified source version, so didn't have a chance to verify the new package.
Does this work for anyone? I am still seeing an empty object for the default export/import.
npm info
> var p = require('purgecss-from-js') undefined > p {} > typeof p 'object' > Object.entries(p) []
When I go back to the old (v0.1.0) release I see a function like I expect:
> require('purgecss-from-js') [Function: PurgeFromJs]
I have the same problem
First of all, thank you for this module. Could save the time as soon as we figure out the reason, why it crashes with the followin error:
TypeError: prepack.prepack is not a function
atnode_modules\purgecss-from-js\lib\purgejs.js:37:35
Please, advice ^_^