-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Parcel v1.7.0 features #132
Comments
|
|
I think you missed about |
Update CLI options to not use 'build' when it is not one of the supported modes. For those who confuse easily 😀 |
Has 1.7.0 has been released? I see |
The docs have been for 1.7.0 for around a week. A prominent version number on the docs pages would be helpful. Devon blogged on 1.7.0. A Blogs or Releases link on the landing page along with current version number would be useful |
@wesleyboar I think most things should be documented, but if you ever run into something you need help with you can always message us on the Parcel slack :) |
I've opened PRs for all the remaining topics :) Closing this in favor of the PRs and #184 (for module resolution) |
This is my initial attempt at resolving #184, #132 and documenting parcel-bundler/parcel#850 I have a few questions which I believe should be answered and better described before merging: - I would like to answer this question in the docs parcel-bundler/parcel#850 (comment) - clarify terminology of: - project root: top-level package.json? - package root: package.json in node_module module? where does this start to resolve from? - these comments https://github.com/parcel-bundler/parcel/pull/850/files#diff-f90b0caefa8028ff5ec8f2f2c2e6e39dR8 seem to suggest I may be missing some important information that should be documented Closes #184
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:
Lmk if I missed anything else that needs to be documented.
The text was updated successfully, but these errors were encountered: