Tests fail on 2nd try
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, rails, webpack
- Domain
- build-system, testing-qa
Research direction
Start by running bundle exec rake twice and compare the generated manifest with 1stPassManifest.json; review tempError.txt for the second-pass output. Inspect commonWebpackConfig.js and the webpack configuration around the extensions setting. Done means the test command can be run repeatedly without the missing client-bundle.css error.
Written by the indexing model from the issue text.
Description
When you run bundle exec rake the first time to run the tests it works well. After it finishes, if you try to run it a 2nd time an error is shown
Puma caught this error: Shakapacker can't find client-bundle.css in /Users/ramezweissa/code/shaka/react-webpack-rails-tutorial/public/packs/manifest.json. Possible causes:
- You forgot to install javascript packages or are running an incompatible javascript runtime version
- Your app has code with a non-standard extension (like a
.jsxfile) but the extension is not in theextensionsconfig inconfig/shakapacker.yml- You have set compile: false (see
config/shakapacker.yml) for this environment
(unless you are using thebin/shakapacker -wor thebin/shakapacker-dev-server, in which case maybe you aren't running the dev server in the background?)- webpack has not yet FINISHED running to reflect updates.
- You have misconfigured Shakapacker's
config/shakapacker.ymlfile.- Your webpack configuration is not creating a manifest.
Full error is in tempError.txt, it contains the manifest generated on the 2nd pass
tempError.txt
This is the manifest which is generated on the 1st pass (which includes client-bundle.css):
1stPassManifest.json
One workaround to be able to run the tests again is to do any edit to commonWebpackConfig.js, for example add ".x" to the extensions.
const commonOptions = {
resolve: {
extensions: ['.css', '.ts', '.tsx', '.x'],
},
};
After this, you can run the tests one time before they fail again
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 370
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 6
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.
More from shakacode/react-webpack-rails-tutorial
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
shakacode/react-webpack-rails-tutorial#731 · 1 comment ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
question
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
All issues in shakacode/react-webpack-rails-tutorial
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100