sinatra / sinatra/sinatra.github.com
Clean up gulp or perhaps consider better options (hint: parcel!)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 299
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
I tried running the CSS compiler and ran into some inconveniences:
-
The browersync watcher starts up for every single invocation. Ideally it should only do that when the user runs
watchor related commands -
Move away from Gulp ruby and use node-sass. The latter is much better supported in the Node ecosystem and avoid the jump between ruby and node.
-
It's worthwhile to consider using a new configless bundler like parcel. I personally found it very simple to use. We can get rid of most of the gulp dependency and package.json also!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing package.json and the existing Gulp CSS compiler and watcher commands. Run the compiler to reproduce the BrowserSync behavior, then compare the requested node-sass and Parcel directions. Done means the build toolchain has an agreed replacement and watch-only behavior, with the package configuration updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, ruby
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100