how to build this? about 30-seconds-of-css HOT 19 CLOSED

@diomed run npm run dev in one tab, then parcel index.html in another tab in terminal/cmd. That should work.

from 30-seconds-of-css.

1. Clone repo and navigate to it
2. Run npm i && npm run dev, open localhost:1234

from 30-seconds-of-css.

This is what I see:

from 30-seconds-of-css.

@diomed Could this be a dependency + node/npm version issue?
With Node=10.6.0 and npm=6.4.1 works fine.

from 30-seconds-of-css.

I get [nodemon] clean exit - waiting for changes before restart
and then nothing happens, after running npm run dev

from 30-seconds-of-css.

I just did a fresh clone and ran the above commands, and it ran with no errors. Are you on Windows maybe? On Mac it works fine, I think it might be because of the parallel processes using the & operator which is Unix only?

from 30-seconds-of-css.

yes, I'm on windows.

first I ran npm i then second command.
Coz I couldn't run both. but still no luck. :|

from 30-seconds-of-css.

Works alright for me on Windows... Can you tell us what exactly you are doing @diomed?

from 30-seconds-of-css.

I did
npm i
then
npm run dev

then I got that error.

from 30-seconds-of-css.

@diomed Sounds like nodemon is closing as it doesn't see anything changed, try adding a space or something to a file somewhere, see if it starts running on save.

from 30-seconds-of-css.

This is all that I get:
https://0bin.net/paste/gTr3D3Ec4bdeki+V#Puyiv13h25JXwY1uOgIPr1OaR0RK36pnN3XLQiauJcl

from 30-seconds-of-css.

Doesn't seem like it's running the parcel process in parallel. We should use the concurrently package maybe

from 30-seconds-of-css.

@atomiks I've never had trouble with this setup (used it in many projects and systems). If we are going to use some package for concurrency, I think npm-run-all is another option as well.

from 30-seconds-of-css.

@diomed Have you run npm i -g parcel-bundler? Maybe try that and tell us if this works for you afterwards. It might be failing silently due to parcel not being installed.

from 30-seconds-of-css.

I tried that, nothing changed. 😕

from 30-seconds-of-css.

If that doesn't work, there's something wrong with your setup most likely. That should definitely work.

from 30-seconds-of-css.

@atomiks that indeed works.
Thank You very much.
Cheers!

from 30-seconds-of-css.

I always get this error:

C:\Users\Parsifal\Documents\GitHub\30-seconds-of-css\scripts\build.js:102
browserSupportHeading.after(
^

TypeError: Cannot read property 'after' of null
at Object. (C:\Users\Parsifal\Documents\GitHub\30-seconds-of-css\scripts\build.js:102:25)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
[nodemon] app crashed - waiting for file changes before starting...

from 30-seconds-of-css.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for any follow-up tasks.

from 30-seconds-of-css.