Skip to content
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

Manually set 1.x versions to 1.1.0 and change Lerna config #305

Merged
merged 1 commit into from
Sep 27, 2018

Conversation

zetlen
Copy link
Contributor

@zetlen zetlen commented Sep 27, 2018

Preparation for 1.1.0 tagging and release.

This PR is a:

[ ] New feature
[x] Enhancement/Optimization
[ ] Refactor
[ ] Bugfix
[ ] Test for existing code
[ ] Documentation

Summary

When this pull request is merged, it will...

  • Change lerna configuration to use fixed version
  • Manually fix package.json versions for root package and public packages
  • Configure public publishConfig for scoped packages

@zetlen zetlen changed the base branch from release/2.0 to master September 27, 2018 14:53
@zetlen zetlen merged commit b2d6757 into master Sep 27, 2018
zetlen added a commit that referenced this pull request Sep 27, 2018
* Check if captureStackTrace exists before calling (#288)

* Check if captureStackTrace exists before calling

* Add test to ensure captureStackTrace isn't called when it does not exist

* Prettier ✨

* Fix failing test (#304)

Unit tests should use MemoryRouter, not BrowserRouter, and do
shallow rendering rather than full mounting.

* feat(dev): Make PWADevServer host/SSL optional (#175)

PWADevServer attempts to create a unique domain name, create local
SSL certificates, and tell the OS to trust those certificates, for
every new project. It also tries to confirm they exist on every run!

This causes many problems for users under some common conditions:
- No administrative access to local machine
- No OpenSSL installed, or wrong OpenSSL installed
- OS cannot be scripted to trust certificates
- Developer uses Firefox, which uses its own cert store

Additionally, some bugs in the implementation have caused some
developers' projects to enter an unusable state.

- Adds `provideUniqueHost` flag to PWADevServer configuration.
 PWADevServer will no longer try to create or retrieve a custom domain
 name unless `provideUniqueHost` is in its configuration in
 `webpack.config.js` as either a custom string or `true`.
- Adds `provideSSLCert` flag to PWADevServer configuration. PWADevServer
will no longer try to create or retrieve a trusted SSL certificate
unless `provideSSLCert: true` is in its configuration in
`webpack.config.js`.
- Modifies custom domain name creation strategy to ensure uniqueness
based on a hash of the full local path, rather than using the local
flat file database.

We created these features for the needs of the developer working on
several PWAs at once on their local machine, so that they don't have to
set up manual SSL every time, and they have no conflicts with Service
Workers. This could be considered "bonus functionality", as it's not
critical to the setup of a minimum viable PWA. It was meant to establish
our focus on developer experience, and articulate the parts of developer
setup that PWA Studio can "own".

*However, we soon learned that we could not maintain all scenarios for
automated setup and continue to make progress with shopper-facing
features*. We still really want to support and automate all of these
scenarios, but for now, our implementations are a hindrance and we are
turning them off by default.

fixup: Documentation edits from PR feedback

* chore: manually set version 1.1.0 and lerna fix (#305)
@supernova-at supernova-at deleted the zetlen/lerna-switch-to-fixed branch July 25, 2019 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants