Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
After running cross-env LIMIT=4096 increase-memory-limit run-node package errors
See original GitHub issueAfter I run cross-env LIMIT=4096 increase-memory-limit I am no longer able to do git commit. This is because I use husky for git -hooks and apparently it uses run-node package. This package gets damaged by cross-env LIMIT=4096 increase-memory-limit and stops functioning. I’m forced to rm -rf node_modules to be able to commit again.
Here’s the error that it gives me:
node_modules/run-node/run-node: line 26: syntax error near unexpected token (' node_modules/run-node/run-node: line 26: has_node --max-old-space-size=4096() {’
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@bartolkaruza’s PR is now avaialble on
increase-memory-limit@1.0.7! 🎉After upgrading to 1.0.7 I have new error - of the same type, but with different package. This time it’s lint-staged package that gets broken.
/node_modules/lint-staged/index.js:9 node --max-old-space-size=4096: ‘>=8.6.0’ ^^
SyntaxError: Unexpected token –
Should we reopen this one or create new?