As parcel is growing and becoming more complete and advanced, it might be usefull to add search to the docs?

Perhaps we could use Algolia's DocSearch? https://community.algolia.com/docsearch/

This will definitely improve the Parcel experience for new users.

cc @devongovett

Hi.

I noticed that pages are loading slowly event though website is not complex.

How about re-create it using Vue.js?

If this idea is fine then I can do it

I'm working on ko-KR translation. But I'm not sure is my translation correct. I need reviewer for ko-KR translation.

Maybe other worker also needs reviewer. I think we must need at least 2 reviewers per languages.

and I think we needs slack channel for converstation between translators. for example, ko-KR translator need #website-ko

Right now the website is hosted from two IPs in AWS us-west-1 in San Jose.

This means everyone who wants to see the website around the world has to make requests all the way to San Jose, and the project is paying for AWS bandwidth, which is expensive.

The free tier of Cloudflare would fix both of these. Or any other CDN, I suppose, but it wouldn't be free.

The [email protected] and [email protected] images on https://parceljs.org/ amount to 1.1MB and 473KB. I would suggest looking into converting them to JPG with some medium-high quality, as that would easily let you reduce their size by ~10x, which would significantly speed up the loading time, especially on mobile.

The description of build machine in "Benchmarks" that in the bottom of homepage is inaccurate. I think "quad-core CPU" is better than "4 physical CPUs" .

Based on a reasonably sized app, containing 1726 modules, 6.5M uncompressed. Built on a 2016 MacBook Pro with 4 physical CPUs.

MacBook Pro - Technical Specifications

I'm really excited about parcel and would like to create a plugin to compile and load protocol buffer files into a bundle.

The problem is that there doesn't seem to be any documentation of the asset loader API beyond an example of the interface shape.

Even looking through the code of other loaders for help it's not really clear what different calls do and when we might use them.

This leaves anyone who might want to contribute to the parcel ecosystem guessing as to how to do that.

If we could just get a few concrete examples of loaders/packagers/plugins using some common API calls (preferably with a brief explanation) that would be super handy.

Thanks for the cool bundler!

현재 제가 번역한 "불꽃 튀게 빠르고"가 사용되고 있는데, "오지게 빠르고" 가 더 본디 의미에 가깝지 않냐는 지적을 받았습니다.

한국어 번역자분들은 어찌 생각하시는지 궁금합니다.

e.g. bundler.on("bundled", ...)

Seems reasonable to use the API for this I think. We should probably document it so people know they can do that though!

parcel-bundler/parcel#800

There is a mistake in the home page.
after 🇨🇳should be 中文, not 俄语.

re: parcel-bundler/parcel#120

We should set the site up to be translated.

I've set some of this up before using Crowdin: https://github.com/thejameskyle/crowdin-sync

Parcel 1.7.0 is coming out soon, and it's gonna be a really huge update with tons of very exciting features and changes! 🚀 😃

The only problem is... none of it is documented yet 😟

I think we should all work together on getting the major changes documented in depth:

• New Resolver (parcel-bundler/parcel#850) - Explain tilde/absolute paths, aliases, etc.
• Auto Install Feature (parcel-bundler/parcel#805) - There's not much to explain, but it's still new concept so we're gonna need to document what it and why it's useful
• New File Naming Strategy (parcel-bundler/parcel#1025) - We should add something to the advanced documentation with that table that @jamiebuilds made in the PR comments

Lmk if I missed anything else that needs to be documented.

We'll translate the parcel website into Japanese!

• <h1> is missing from the page
• <h2> is used improperly - text under Parcel logo is just a subtitle, and not actual heading
• Language "dropdown" is not actual dropdown, which makes it impossible for keyboard users to use it.
• Language "dropdown" values are emoji, which are not good for screen readers. If you absolutely have to use emojis, use <abbr> tags as well.

I am currently playing around with Parcel on a new React app I created. Almost everything I do in JavaScript, I do in TypeScript. With that being said, I take advantage of Module Resolution. I know that absolute paths/imports were finalized in the 1.7.0 release and in this PR, but I'd like to document this.

I read some comments and while I can respect different perspectives, I know that for larger projects I work on, it's important to use absolute imports or the imports themselves get too deep/convoluted. Trying out the solution in the PR mentioned above, I do have absolute imports working but my IDE (VS Code) is going crazy with errors. This doesn't affect the actual app running but can be distracting when I am trying to debug. I think a new section on module resolution / absolute imports with Parcel can help developer experience and adoption with Parcel. (This was the biggest reason I didn't try Parcel. I just learned that this feature existed the other day.)

I can't commit to having this PR in an hour or even a week. I'd like to fully understand how everything works so I can provide some stellar docs for other people. If this sounds good to project maintainers, please let me know! Thanks for all the hard work, ladies and gents.

This merged feature is very useful, maybe we can add a simple documentation on the "Advanced" section about this feature.

npm install causes the following:

$ npm install
npm WARN deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support

[email protected] postinstall C:\xxx\xxx\xxx\xxx\website\node_modules\now
node download/install.js

For the source code, check out: https://github.com/zeit/now-cli

Downloading Now CLI 8.5.4 [ ] 0%
{ Error: incorrect header check
at Zlib.zlibOnError [as onerror] (zlib.js:142:17) errno: -3, code: 'Z_DATA_ERROR' }
Downloading Now CLI 8.5.4 [ ] 0%
{ Error: incorrect header check
at Zlib.zlibOnError [as onerror] (zlib.js:142:17) errno: -3, code: 'Z_DATA_ERROR' }
Downloading Now CLI 8.5.4 [ ] 0%
{ Error: incorrect header check
at Zlib.zlibOnError [as onerror] (zlib.js:142:17) errno: -3, code: 'Z_DATA_ERROR' }
Downloading Now CLI 8.5.4 [ ] 0%
{ Error: incorrect header check
at Zlib.zlibOnError [as onerror] (zlib.js:142:17) errno: -3, code: 'Z_DATA_ERROR' }

Please add a TypeScript icon (background color #0074c1) for the box animation on the landing page.

Warning, total noob question: I forked the repository, cloned it to my machine, ran npm install inside its root folder, then npm start to run the server (?). This is what I get back from my terminal:

> [email protected] start /Users/rah/Dropbox/www/sites/parcel-website
> node src/server.js

fs.js:904
  return binding.readdir(pathModule._makeLong(path), options.encoding);
                 ^

Error: ENOENT: no such file or directory, scandir '/Users/rah/Dropbox/www/sites/parcel-website/src/../dist'
    at Object.fs.readdirSync (fs.js:904:18)
    at Object.<anonymous> (/Users/rah/Dropbox/www/sites/parcel-website/src/server.js:5:22)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:612:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node src/server.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/rah/.npm/_logs/2018-08-17T17_49_07_768Z-debug.log

Any idea or hint, what I'm doing wrong?

Hi, I haven't found any issue related to spanish docs, so I've decided to team up with @albizures to translate the site.

🙋 feature request

While current documentation is sufficient for simple use cases,
it is not very clear how parcel handles all possible file extensions.

For example PostCSS has option to use custom parser and you usually use different file extension for it.

🤔 Expected Behavior

Asset Types to describes all assets that are recognized by default

😯 Current Behavior

Not done

💁 Possible Solution

I'm not sure how well it would be suited, but I'd like to see table with all possible file extensions with description how Parcel treats them

🔦 Context

I was trying to convert my old webpack project to use parcel as I mostly need to convert bundle some CSS only.

It turns out that I cannot properly handle CSS with multiple sources of different types(e.g. plain CSS and SugarSS)

As I'm not sure how exactly PostCSS assets are recognized, I'm unsure how to approach my problem

💻 Examples

hi parcel team

I want to translate to Turkish if nobody started already.

The file watcher gets buggy when used inside an environment that utilises safe write like gedit on ubuntu and some other editors, we should document this so people don't run into this issue presuming it's a Parcel bug.

We tried to detect this automatically, but with no luck so far, related issues:
parcel-bundler/parcel#221
parcel-bundler/parcel#238

I notice that the changes I made are not applied on the site parceljs.org, should not an update be launched (deploy, "zeit now)?

Here is the list of changes that are not applied on the site:

• Fix typo first sylvainpolletvillard review 3f84f95 (Commit on Apr 30, 2018)
• Update translation in french cb233a5 (Commit on May 5, 2018)
• Update translation in french f69debe (Commit on May 18, 2018 )

Looks like support for source-maps just landed - is it documented?

Location:
https://en.parceljs.org/
https://ko.parceljs.org/

Alignment:

Hover Styling:

Hi guys! May I send a PR soon with the Italian translation? 😃

Hi.

I have a question.
Do you have a regular process to register translated files?
If you have, I want to apply.

I'm translating parceljs.org into Korean. I'm going to complete this work in a week.
Here is a demo and its repository.

The og:image is not defined, and is currently showing parts of the box in the main page. I am not sure who could define and implement this media concerns for the web, I just want to surface this.

This is the preview images that facebook detects:

For this page https://en.parceljs.org/recipes.html

Would it be possible to make an Angular recipe as well. (even a bug-ridden wip one with a big fat disclaimer) ?

🙋 feature request

Can you help to take off the parcel official web National flag in front of the language select ?

🤔 Expected Behavior

😯 Current Behavior

🔦 Context

Hello, I am a Taiwanese user ( from Taiwan 🇹🇼 ). I like Parcel and its official web, and feel happy that provide multi language version.

But when I wanted to change web language to change to Chinese version, I saw the National Flag of PRC (🇨🇳) in front of the Chinese option (中文). I feel not good and disagreeable😵😰😱, cause I am Taiwanese but not Chinese.

Malaysia (🇲🇾) , Singapore (🇸🇬) and Taiwan (🇹🇼) all speak Chinese, BUT we are definitely not the people of P.R.C. .
Other case: British (🇬🇧), Canadian (🇨🇦), and other country that use English as official language (👉see here) are not American of USA (🇺🇸).

So, I just suggest you to take off the National flag from language select list, Thank you.🙏

💻 Examples

👉 yarn official web

Hello, Parcel team!

I want to translate to Ukrainian, if nobody started already.

Hey guys, do you think is worth to add a npm script like npm server that will build the project and set it up, instead of to do it manually?
Just a suggestion.

Hello,

Does someone is working on Vue.js recipes (ru) documentation?
I can translate it.

Regards,
Maksim

Using Google Chrome 62.0.3202.94 on Windows 10 the "Get Started" and "Github" buttons on https://parceljs.org/ are only clickable on the lower half of the button.

Hey, contributors, I would like to open discussion of restructuring the documentation.

Things I've liked about the current docs:

• concise
• clear distinction about terms

Things I would like to contribute to and see improved:

• separate usage from creating (eg plugins)
• describe the default features and how each OOTB tool is supported
• 0 config is great, but ultimately users still need to understand how it all works

I feel like the overall docs would benefit from a restructuring, namely a better separation of the user/creator information.

Here is a suggestion I have thought about while contributing over the last few days:

nav headings with descriptions of topics

this is my idea of a restructure:

getting started

• quick start
  explaining simple setup, dev use & prod output
• assets & transforms
  explain what an asset & a transform are
  use an image to explain (make it shorter than existing Assets section)

features

• code splitting
• hot module reloading
• production bundling
• cli

out of the box support

• default asset types
  list of asset types, their associated file extension(s) and common tools they support. each item in the list links to a page for that asset type
• env vars
• module resolution
• using plugins

asset types

• ...asset-type item (ie: JavaScript, ReasonML...)
  what tool is used to support this (this matters when talking about feature support and improving on the asset's ecosystem within Parcel)
  the config files used by the underlying tool
  default transforms that apply to the asset
  embed some codesandbox.io examples maintained via https://github.com/parcel-bundler/examples

create

• how it works
• assets & parsers
• plugins
• packagers
• bundler api

EG

This is just an idea, so feel free to turn it down, but please note that I will happily do this work, it's a request to contribute. I'm very passionate about documentation and figure what better way to learn the inner-workings of Parcel 😄

If you would like to see what or how I would structure some of the specific "asset types" pages content I'll happily write one up as a further example.

Other considerations alongside a restructure:

• search, as raised in #193, would make this much nicer to find information on say, flow which would be mentioned under the JavaScript page and not have it's own top-level page.
• need css for the left nav to scroll independently of the content.

❔ Question

I have found that official instructions to use Babel + Parcel, may be wrong or misleading.
This is a text fragment from Parcel's web page.

Install presets and plugins in your app:
yarn add babel-preset-env

These instructions can be found here, within the Babel section.

Since Babel already includes the babel-preset-env module, as a dependency, installation of this module is not necessary. The only thing you need to add, is a .babelrc config file.

🌍 Your Environment

Today (12/28/17) I went to parceljs.org looking for the docs. Visiting https://parceljs.org/ returned a 500 error code.

I assume you're already aware of this, but I didn't see an issue for it. I wish I could provide more info, but HTTP error codes don't say much on the client end -

The project looks fantastic, and I'm excited to see what it can do :)

Ubuntu 16.04
Firefox 57

Just mention somewhere (probably in cli) that parcel support multiple input/entry points via list or glob.

(It will prevent this: parcel-bundler/parcel#1239)

Just so you know, I'm on it at the moment :)

At present, the .language-dropdown is using national flags via emoji, such as 🇺🇸, U+1F1FA REGIONAL SYMBOL INDICATOR LETTER U followed by U+1F1F8 REGIONAL SYMBOL INDICATOR LETTER S. GitHub may replace it with an image here because these emoji are poorly supported; but quite apart from the matter of poor support for the emoji—

Flags are not languages.

This should be changed to use the name (e.g. “English”, “한국어”) of the language instead. (You could get away with using the ISO 639-1 code (e.g. “en”, “ko”) too, but it’s not as good as just the name of the language.)

Maybe add a favicon of your logo so the site looks better/more professional.

Also the icon in front of the title seems to be broken.

Perhaps based on the examples I wrote for the announcement article: https://medium.com/@devongovett/parcel-v1-5-0-released-source-maps-webassembly-rust-and-more-3a6385e43b95

Based on current docs it's not clear if one could require scss from html or not:

CSS

CSS assets can be imported from a JavaScript or HTML file ... In addition to plain CSS, other compile-to-CSS languages like LESS, SASS, and Stylus are also supported, and work the same way.

SCSS

... Once you have node-sass installed you can import SCSS files from JavaScript files ...

parcel-bundler/parcel#1278 (comment)

Website already has Russian translate, but quality isn't very good. I want to rewrite it on New Year's holidays. Stay tuned!

As in title.

Speaking of language dropdowns, I think it definitely shouldn't be "translated", it should have its own place in the code. Ideally, the list could be automatically generated based on available languages. Such code duplication just asks for bugs in the future.

Hey! I really like the layout of the site and I've been meaning to use it for a project of mine (totally unrelated to Parcel however). Particularly, the top-menu section and the general-layout of it.

Could you please add a LICENSE to the site? (I'm assuming MIT you'd probably use).

Many tanks!