So, right now there are a lot of basic questions which users have. It would be great to have a wiki page for the FAQs.
Any suggestions?
@reznord This sounds great , I can look through the issues and see what issues are the most common and fixable to add there , that sound good ? 馃槃
First thoughts: Custom Templating, Customizing Webpack
Even though both those are in the README, might want to rip out all "How-Tos" from there & point to this new Wiki section instead, along with the existing Recipes section.
@SaraVieira Totally, sounds great.
Another thing, we need to mention that _Master branch is for development purposes._
@reznord Agreed, that should go at the top of Readme imo. Seen that pop up 2 or 3 times.
Yeah, I am just starting with preact (with basic experience with react, and basic experience with the javascript ecosystem), and have a load of newbie questions, and would love to see something like this added.
I'll be happy to add to it as well, as my experiences would be pretty common, I think.
Sure, that would be great.
Go ahead and create a page in Wiki Section :)
@joshuataylor that would be great. We can answer but we don't know the question
Edit: I created a page here https://github.com/developit/preact-cli/wiki/FAQs
Feel free to edit it
@thangngoc89 I meant more like I would document my experiences and pitfalls I find to help others :).
@joshuataylor I created a page for it. And that would even more awesome
Hello guys! I'll go through the issues today and send them through slack because I can't edit the wiki pages 馃檨
_Sent from my Bq Aquaris M5 using FastHub_
Hey @developit,
If you have time, could you go to project setting and uncheck Restrict to collaborators only?

If you have time, could you go to project setting and uncheck Restrict to collaborators only
Just sharing my 2 cents tho, We can but that might be a problem in the future since the Wiki is open to public and anyone can come down and write any sort of stuff they want.
@reznord If no one can edit the Wiki then we should move Wiki back to the repo and accept editing via PR? Even though wiki is a git repo itself, there is no UI for sending PR
We can add a docs folder (or its own repo) and modify preact-www to serve that on the site under a Preact CLI section.
Pointing to https://github.com/developit/preact-www/issues/152 because it falls inline with this approach.
@skaraman You can just modify the webpack config directly inside your preact.config.js:
export default (config, env) => {
config.node = {
process: 'mock'
}
}
See https://github.com/developit/preact-cli/issues/244#issuecomment-316558813 and Wiki for reference.
@lukeed @reznord @thangngoc89 I made a gist with the questions I found that already fixable : https://gist.github.com/SaraVieira/ab76cd4258a1e77c75829c6b38aa2ab1
updated the gist so that it's waaaay more readable
@SaraVieira
The Readme in Github and NPM
It's not right. npm readme is always the up-to-date version of preact-cli. Only Github master README is not released yet.
@thangngoc89 True !
Updated the gist:
https://gist.github.com/SaraVieira/ab76cd4258a1e77c75829c6b38aa2ab1
Regarding #309 it would be great to add a snippet on how one can extend the webpack config using preact.config.js for classnames support in various folders (other than routes & components).
more on config, how can one configure a custom loader like https://github.com/kossnocorp/defile#configuration
?
You can install or define your own loaders same as any webpack project:
// preact.config.js
import path from 'path';
export default (config) => {
let myCustomLoader = path.resolve(__dirname, 'path/to/my-custom-loader.js');
// introduce the loader:
config.resolveLoader.alias['my-custom-loader'] = myCustomLoader;
};
Then use it like so:
import foo from 'my-custom-loader!./foo';
Added the FAQs in the wiki, please feel free to drop any other common questions that needs to be answered.
A huge thanks to @SaraVieira
Most helpful comment
We can add a
docsfolder (or its own repo) and modifypreact-wwwto serve that on the site under a Preact CLI section.Pointing to https://github.com/developit/preact-www/issues/152 because it falls inline with this approach.