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

chore: 🤖 Yarn upgrade, tsdx and docz version bump #36

Merged
merged 1 commit into from
Jan 31, 2020
Merged

Conversation

DanweDE
Copy link
Contributor

@DanweDE DanweDE commented Jan 30, 2020

To use .jsx files in the upcoming rich text field editor we need tsdx 0.12 together with the workaround mentioned on jaredpalmer/tsdx#443

@DanweDE DanweDE force-pushed the bump-tsdx branch 3 times, most recently from ba64a80 to 39bce2b Compare January 31, 2020 00:00
@DanweDE DanweDE changed the title chore: 🤖 Bump tsdx version to 0.12.0 chore: 🤖 Run yarn upgrade + tsdx and docz verision bump Jan 31, 2020
@DanweDE DanweDE changed the title chore: 🤖 Run yarn upgrade + tsdx and docz verision bump chore: 🤖 Yarn upgrade, tsdx and docz version bump Jan 31, 2020
@DanweDE DanweDE requested a review from suevalov January 31, 2020 08:48
@@ -31,7 +31,7 @@ export function MultipleLineEditor(props: MultipleLineEditorProps) {
error={errors.length > 0}
disabled={disabled}
value={value || ''}
onChange={(e: React.ChangeEvent<HTMLInputElement>) => {
onChange={(e: React.ChangeEvent<HTMLTextAreaElement>) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

package.json Outdated
@@ -77,7 +81,7 @@
"remark-preset-lint-recommended": "^3.0.3",
"remark-validate-links": "^9.0.1",
"start-server-and-test": "^1.10.6",
"tsdx": "0.11.0",
"tsdx": "0.12.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is 0.12.3 available already. do we need 0.12.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I'll look into that.

@@ -1,3 +1,4 @@
import noop from 'lodash-es/noop';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd import `import noop from 'lodash/noop' as we do in other places. TSDX transforms it to tree-shakable thing automatically

https://github.com/jaredpalmer/tsdx#using-lodash

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I already tried that but I got

    SyntaxError: Unexpected token 'export'

    > 1 | import noop from 'lodash-es/noop';
        | ^
      2 | import React, { useState, useCallback } from 'react';
      3 | import { css } from 'emotion';
      4 | import tokens from '@contentful/forma-36-tokens';

While already spending too much time on all of this chore stuff I decided not to look into it. If you can point me at how to solve this without lots of trial and error let me know and I can do.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd leave it as it is then :)

- To use .jsx files in the upcoming rich text field editor we need tsdx
0.12 together with the workaround mentioned on
jaredpalmer/tsdx#443
- Use docz 1.3.2
- Ran `yarn upgrade`
@DanweDE DanweDE merged commit c97ef3e into master Jan 31, 2020
@DanweDE DanweDE deleted the bump-tsdx branch January 31, 2020 14:10
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.

2 participants