Open hwanderlust opened 6 years ago
Hi @hwanderlust
Okay just added babel
to the build process and pushed version 1.1.17
to npm. Let me know if this works for you!
https://github.com/stephenlb/spoken/commit/4e0712f6eec3a742dc9e37e943a37fa0f34fde72
Hi @hwanderlust did this recent upgrade fix your issue?
It did not unfortunately. Same error message.
We followed the instructions. Is there some special command we should use? The instructions in the link provided do not indicate more steps.
I'm not quite sure. I'm new to this--I thought it might've been my windows setup, but couldn't find a solution.
On Tue, Sep 25, 2018 at 3:59 PM Stephen L. Blum notifications@github.com wrote:
We followed the instructions. Is there some special command we shod use? The instructions in the link provided do not indicate more steps.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/stephenlb/spoken/issues/3#issuecomment-424480672, or mute the thread https://github.com/notifications/unsubscribe-auth/AkogWdpJpymDiJOorYp1MgLUiiYIeGguks5ueosdgaJpZM4Wp-oZ .
-- Regards,
Paul Ly
Creating an optimized production build... Failed to compile.
Failed to minify the code from this file:
Read more here: http://bit.ly/2tRViJ9
npm ERR! code ELIFECYCLE npm ERR! errno 1