Disable merging and minification steps in the build process
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- build-system, developer-experience
Research direction
Start by locating the build process that combines generated and manually adjusted React component code, then find where the resulting code is minified. Disable both steps and verify that packages expose the original, unaltered source so IDEA can navigate the JavaScript correctly.
Written by the indexing model from the issue text.
Description
We've recently received a user request for access to the source code of our React components, as discussed in this forum thread. Currently, the code for each component is divided into two sections: a generated portion and a manually adjusted section for instances that require specific tuning. During the build process, these two sections are combined and subsequently minified.
This process, however, disrupts the mapping algorithm of IDEA, making it exceedingly difficult to navigate through the JavaScript code. Therefore, the proposal is to disable both the merging and minification steps during the build process. This would allow us to provide the end user with the original, unaltered code.
- Dominant language
- TypeScript
- Stars
- 18
- Forks
- 4
- Avg merge
- 52m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from vaadin/react-components
-
Impact: Low Severity: Minor UX
Difficulty 4/5 3-5 days Newbie friendliness 68/100
vaadin/react-components#407 · 2 comments ·
-
bug Impact: Low Severity: Major
Difficulty 4/5 3-5 days Newbie friendliness 48/100
vaadin/react-components#398 · 1 comment ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
vaadin/react-components#338 · 1 reaction ·
-
hilla react
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
vaadin/react-components#337 · 8 comments ·
-
bug Impact: Low Severity: Major
Difficulty 3/5 1-2 days Newbie friendliness 50/100
vaadin/react-components#323 ·
All issues in vaadin/react-components
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
betagouv/mon-entreprise#4699 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jaegertracing/jaeger-ui#4547 · 3 comments ·
Maintainers usually reply within 1 day
-
ai-driven-qa
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1467 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
need4deed-org/sdk#267 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/universal-login#414 ·
Maintainers usually reply within 1 day