Skip to content
This repository has been archived by the owner on Mar 30, 2021. It is now read-only.

Unclear developer experience #4

Open
LakshSingla opened this issue Mar 17, 2019 · 3 comments
Open

Unclear developer experience #4

LakshSingla opened this issue Mar 17, 2019 · 3 comments

Comments

@LakshSingla
Copy link

LakshSingla commented Mar 17, 2019

(NOTE: This issue can be broken down into many different interconnected issues, but for sake of keeping things simple, I have jotted down what all I felt was wrong here)
I was trying to setup a development server. But it took me a while to figure out the following things-

  • One has to run less first. Only then build or start will be successful.
  • Since less is not added to the webpack.config.js thus in case someone has changed his styes, he or she will have to run less again.
  • Custom dev server is being used, instead of the one being provided by webpack. The webpack one automatically refreshes the webpage and in some browsers also clears the cache (last time I used it). It will help in cleaning the directory of files which the developer doesn't need.
    One optimal solution includes updating the webpack.config.js to include less and serve tasks.

(Somewhat unrelated)

  • On the examples, the class of the component one creates is not added to the examples component. Hence the custom styles are not.
@sarthak-sehgal
Copy link
Contributor

@Nikhil-Vats is this is relevant now?

@Nikhil-Vats
Copy link
Member

Yes, this is still relevant.

@Nikhil-Vats
Copy link
Member

One part of the issue is solved (see PR above) -

On the examples, the class of the component one creates is not added to the examples component. Hence the custom styles are not.

The rest are still relevant.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants