maizzle / framework

Quickly build HTML emails with Tailwind CSS.
https://maizzle.com
MIT License
1.24k stars 49 forks source link

No 'config.undefined.js' file found #35

Closed pazitron1 closed 5 years ago

pazitron1 commented 5 years ago

Description:

The maizzle/framework v 0.3.0 has the following issues when running maizzle serve:

(node:17474) UnhandledPromiseRejectionWarning: Error: No 'config.undefined.js' file found (node:17474) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) (node:17474) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code

Steps To Reproduce:

Update/install maizzle/framework v.0.3.0 Create new maizzle project and cd run maizzle serve

Workaround

in your terminal run touch config.undefined.js then maizzle serve

cossssmin commented 5 years ago

Crap, I think I know what caused it. Thanks for flagging, I’ll fix it next week when I return from vacation.

cossssmin commented 5 years ago

Fixed in v0.3.1, make sure to update and thanks again for letting me know 👍

happysalada commented 5 years ago

@cossssmin I've got the same issue still. Here are the exact steps I took

# install maizzle
yarn global add @maizzle/cli
maizzle new my_project
cd my_project
maizzle serve

maizzle cli version: 0.1.2

Anything I forgot to do? I just followed the official tutorial

cossssmin commented 5 years ago

Can you please run npm list @maizzle/framework in your project, and let me know what framework version are you using?

happysalada commented 5 years ago

@cossssmin thanks for the help! The framework version was actually the old one. on a fresh install for a new maizzle project it seems to default to the old framework version, that tricked me. Thanks for your time!

cossssmin commented 5 years ago

Cool, happy to hear it worked. I should update that package-lock.json on the starter...