dwyl / dwyl/learn-closure-compiler
Why?
Open
Nobody has claimed this yet.
enhancement
help wanted
question
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Before we dive into learning about Closure Compiler, we need ask ourselves the question: Why?
- Why is this useful?
- What "problem" is this solving?
- Did the users ask us to write the code using ES6 features, or is this a developer "requirement"...?
- Is there a use-case for "compiling" JS code regardless of if we are using ES2015/17 ?
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named in the issue. Start by reviewing the repository's existing learning content and the single comment, then determine whether this question should become a documented explanation of Closure Compiler's purpose and use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100