codesandbox / codesandbox/codesandbox-client
Console.time almost always shows 0ms in CodeSandbox console - but real results are available in the browser's console
Open
Nobody has claimed this yet.
External Dependency
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the
Contributing Guidelines
for this project. - I agree to follow the
Code of Conduct
that this project adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
I'm doing some benchmarking and I noticed that when dealing with times like 24000ms, instead CodeSandbox shows 0ms, or in some cases 1ms.
To Reproduce
Link to sandbox: https://codesandbox.io/s/infallible-tdd-ex27s?file=/src/index.js
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | |
| Browser | Firefox 82 |
| Operating System | Windows 7 |
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 with the linked sandbox entry point, src/index.js, and reproduce the console.time case in CodeSandbox while comparing it with the browser console. Trace how the timing output is collected and displayed; done means durations such as 24000ms are reported accurately rather than as 0ms or 1ms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100