You are viewing a single comment's thread from:

RE: Boilerplate For React Applications Using Atlaskit Components And Parcel

in #utopian-io8 years ago

Hey @cutemachine - thanks for this - you're continually introducing me to new tools! I'm really becoming a fan of Parcel since you last posted about it. I'll have a crack at AtlasParcel too.

Sort:  

Hello Steve, glad that my posts are helping you on your way. Yes, Parcel is fantastic. I lost so many years configuring Webpack and other bundlers :)

Parcel is so liberating. Now​ I have time to program instead of tinkering my configuration.

Parcel + Babel > Typescript?

I saw in one of your posts that you are using Typescript. Why do you prefer it over plain JavaScript?

LOL. I asked you first. Ok, I'll go. I like typescript because that's just the order of things. I was working with coffeescript, and typescript came soon after to get my attention. Basically, it's what I know. Things I like about typescript:

  • Tooling
    • tsc for compilation
    • ts_node for runtime execution without compilation
    • sass support
    • webpack integration
  • type declarations. It's easy to add my own types and ts just takes care of the rest. For example, steem wasn't typed and it was easy for me to just add it. That was really nice.

Things I don't like about it

  • It's freaking voodoo. I don't mean compiling to js. Since it is adding integration for already confusing (webpack) aspects of how that works and getting through hairy situations are not an option (at least not for me). This means that in some exceptional cases, I still fall back to plain old JS because I can't figure it out.
  • effing semicolons!!!! Take the javascript out of javascript why don't you!!!

​LOL, yes that's true, you asked first ;)

I'm sticking to JavaScript because I like it. I use Babel in all of my projects. Therefore I can use the latest features of the language. And there have been significant additions to the language like the modules syntax and spread operators.

Furthermore, I do not believe in static types. I prefer developing with dynamic types. There is less noise in my code. When I say I do not believe in static types I mean that I do not believe that static types will bring down your error density. If you want to bring down the error density in your programs, use TDD.

I have not used semicolons in my JavaScript program in years, and I had not a single issue with it.

But I agree with you on the tooling. I have seen some great tooling for TypeScript. But there are static analyzers which give you most of the benefits for JavaScript as well.

So to sum it up: I'm just happy using JavaScript :)

I really want to give atlaskit a try. I think this is my gateway drug. I'm going to give it a try. Thanks for pushing it on to me.

benadryl.png

:) Let me know what you have built.

PS: I will update the starter to include Redux for state management.

Do you know how to solve this? I'm running into this with npm run build

> [email protected] build /app
> parcel build src/index.html --public-url ./

⏳  Building...

⏳  Building index.html...
⏳  Building index.js...
⏳  Building MainRouter.js...
🚨  /app/src/modules/MainRouter.js:26:23: Unexpected token (26:23)
  24 |   }
  25 | 
> 26 |   appWithPersistentNav = () => (props) => (
     |                        ^
  27 |     <App
  28 |       onNavResize={this.onNavResize}
  29 |       {...props}

I added it as the default dashboard to my the docker image I use for my bots. https://github.com/r351574nc3/docker-steem-bot-template/releases/tag/0.1.0-atlasparcel

I also started a new steemit-events project to use it. It's an event app for steemit blockchain.

Coin Marketplace

STEEM 0.09
TRX 0.30
JST 0.034
BTC 113713.87
ETH 4084.09
USDT 1.00
SBD 0.59