preact build --json fails with `TypeError: c.getModules is not a function`
See original GitHub issueDo you want to request a feature or report a bug? bug
What is the current behaviour?
preact build --json
fails with TypeError: c.getModules is not a function
If the current behaviour is a bug, please provide the steps to reproduce.
I made sure I have latest preact-cli and webpack, etc. I created a new preact-cli app with preact create default my-project
ran preact build --json
got error.
What is the expected behaviour? to actually output build stats json file
Please mention other relevant information.
- Node version v9.4.0
- npm version 5.6.0
- Operating system MacOS 10.13.2 (17C205)
- webpack version 3.10.0
- CLI version preact-cli 2.1.1
- Browser
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
how to fix cb.apply is not a function, npx + preact-cli
I'm trying to create a new project with preact-cli : npx preact-cli create typescript temp. It fails with the error message:
Read more >preact-cli: Versions - Openbase
Full version history for preact-cli including change logs. ... Webpack error message for c.getModules is not a function (#472): a1d909a Thanks @developit!
Read more >preact-cli - npm
When a new template is added to the organization, you will be able to run npx preact-cli create <template-name> <project-name> to use that...
Read more >Falcon Sandbox v8.49.7 © Hybrid Analysis
Analysed 3 processes in total. rundll32.exe "%WINDIR%\System32\ieframe.dll",OpenURL C:\6af95dcd80000e3ceee1cc67a679439bf7704d79771ebb4ea510c68c0d68dd70.url (PID ...
Read more >747 kB - Hugging Face
Ġis Function Ġren dered tegra tions provides Module Ġre ferences de st ule ... Fail ures Ġ1 000 c ting ))} ); ]...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This looks a lot like a regression that occurred between 2.1.0 and 2.1.1 Today I realized my website wouldn’t build on Netlify’s CI while it was building fine locally. I was running react-cli 2.1.0 locally while Netlify was installing react-cli 2.1.1 I tried updating my local react-cli to 2.1.1 and the
TypeError: c.getModules
appeared. I downgraded immediatly after back to 2.1.0 and build worked as expected, both locally and on Netlify.Current workaround: downgrade to react-cli 2.1.0
mapModules
is still usable, onlygetModules
is deprecated. So I guess ternary is safe.