pasobob.blogg.se - Webpack documentation github

#WEBPACK DOCUMENTATION GITHUB HOW TO#
#WEBPACK DOCUMENTATION GITHUB UPDATE#
#WEBPACK DOCUMENTATION GITHUB DOWNLOAD#

It's similar to a replace but a bit more clever. Replace modules with other modules or paths.Įxpects an object with keys being module names. Options affecting the resolving of modules. Sadly it looks like I can't get the data about that currently: npm/download-counts#6 :(Īnd if you really want to point out that "webpack 2 has not been released yet" and maybe shouldn't even be used, it should be the first line on the current README.md.Resolve As long as it is public and released in beta version it is released (imho).

#WEBPACK DOCUMENTATION GITHUB DOWNLOAD#

I would love to see stats about how many people download v1 and v2 last week, to really find out if "webpack 2 has not been released yet -> no link yet." is an important argument. The docs could link to the correct blog and could say that a Twitter account is planned, but currently available, because the name is taken. ( was new for me and I just asked yesterday about an Twitter account. If development for happens on master the README.md should reflect this (imho). ĭocs for will be released on, but they are currently in a beta phase, too. If you're looking for documentation of you can visit () or. We're currently working on While it is in a beta phase we recommend to only use fix versions of as every beta release could break your build. I personally would add a note to the README.md on master similar to this: IMHO the current README.md should be all about and not about anymore. Things like that could be added to the README.md as well. Why not make the difference clear in the docs for everyone? Why not add this to the docs? "Hi, these are the docs for New docs for will be released at a later time." As far as I know many people use even if it is a beta for several months. The old docs have no version number, because there is currently only one release version (1.x). Docs for webpack 2 could be labeled as beta versions themself or a lack of docs for version 2 could be made explicit until version 2 becomes stable (however that would not be true - there are a lot of (beta) docs about version 2). It is released with more than 30 beta versions.

Webpack 2 has not been released yet -> no link yet. But in my opinion some statements are a little bit weak (no offense!). I do know and others are working hard on itself and the docs. I think there is a lot of value in the things and #1545 (comment) said. And I don't often have the time to sift through references in a pull request to a non-linked repo somewhere.

It's just I've been trying to find info on Webpack 2 and have come up with nothing repeatedly.

the timeline (however tentative) for the release.

that its docs are moved to a different WIP website, with a link to the website.

Nowhere is there a clearly stated section/page/sentence: However you search for it, the only information you get on webpack / webpack 2 are: The webpack 2 page is open-source: Just write the content, that you feel is missing. If you just want to try out vue-loader or whip out a quick prototype, use the webpack-simple template instead. Make sure to also read vue-loader 's documentation for common workflow recipes. For all intents and purposes webpack.js.org doesn't exist:Ĭomplaint: "update docs to clearly state which version of webpack they refer too" This boilerplate is targeted towards large, serious projects and assumes you are somewhat familiar with Webpack and vue-loader. Because the only info about this website is available in this issue. Just write the content, that you feel is missing. All links are to the 1.x documentation.įor all intents and purposes the master branch is version 1.x Unless, of course, webpack 2 is just a testbed and is not intended for public use

move information on webpack 2.x from gists, unfinished pages and Google docs (really? really? google docs?) to the place where they can be easily viewed and accessed by everyone.

#WEBPACK DOCUMENTATION GITHUB HOW TO#

(there are already people asking how to use, say, LoaderOptionsPlugin, see comments here

#WEBPACK DOCUMENTATION GITHUB UPDATE#

update docs to reflect changes in plugins, loaders etc.

create page clearly detailing what 2.x is, how to get it etc.

update docs to clearly state which version of webpack they refer two.

However, I'll rephrase it and ask for the following: The most obvious question is, of course: how can a project be 2.1 when there's exactly 0 readily available information on 2.x?

there are no announcements, news or documentation referring to 2.x.

the master branch is apparently 1.x (if you trust the npm badge, there's no other version info in the README).

webpack website carries no version info and is apparently 1.x only.

Looking at the release page one can see that version 2.1.0 is well under way.