Skip to content
This repository was archived by the owner on Mar 4, 2020. It is now read-only.

chore(CI): reenable test:projects:cra-ts #608

Merged
merged 5 commits into from
Dec 14, 2018

Conversation

layershifter
Copy link
Member

@layershifter layershifter commented Dec 13, 2018

This PR reenables previously disabled test:projects:cra-ts, #549.

@@ -167,7 +124,7 @@ task('test:projects:rollup', async () => {
task(
'test:projects',
series(
// 'test:projects:cra-ts', Temporary disabled
'test:projects:rollup',
series('build:dist', 'test:projects:pack'),
Copy link
Member Author

Choose a reason for hiding this comment

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

yarn gulp build:dist and yarn build:dist do the same work, if we do it there as Gulp's we will avoid double transpilation with ts-node 🚀

}

export default App;
`
Copy link
Member Author

Choose a reason for hiding this comment

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

We have now a separate folder for this 👍

await sh(`yarn pack --filename ${packageFilename}`)

logger(`Stardust package is published: ${packageFilename}`)
})
Copy link
Member Author

Choose a reason for hiding this comment

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

We will run test:projects:pack only once for both tests 🚀

@DustyTheBot
Copy link
Collaborator

Warnings
⚠️ There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

Generated by 🚫 dangerJS

@@ -9,23 +9,12 @@ import config from '../../../config'
import * as tmp from 'tmp'

const { paths } = config

const log = msg => {
Copy link
Contributor

Choose a reason for hiding this comment

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

now the output is indistinguishable, it is very hard to understand what is going on and immediately find the step necessary:

image

It will significantly complicate debugging scenarios

Copy link
Member Author

Choose a reason for hiding this comment

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

Agree, I restored your logger

console.log('CRA TS:', msg)
console.log('='.repeat(80))
}
let packageFilename
Copy link
Contributor

@kuzhelov kuzhelov Dec 13, 2018

Choose a reason for hiding this comment

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

don't like this broken encapsulation between the tasks, especially given that all can be tried to use in isolation. This implicit composability assumptions would be really hard to track - thus, would prefer correctness there at the first place

Copy link
Member Author

@layershifter layershifter Dec 13, 2018

Choose a reason for hiding this comment

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

I'm not so familiar with Gulp, do you have a better approach there? How I can pass a name between tasks?

Copy link
Member Author

Choose a reason for hiding this comment

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

Nevermind, yarn pack is quite fast so I moved it back to each step.

Copy link
Contributor

Choose a reason for hiding this comment

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

@layershifter, thanks - unfortunately, there is built-in support in gulp to produce result from task (just in a form of artefacts, but this is definitely not what your question about:) As alternative, we might consider cache semantics, but absolutely agree that it is better to split, especially if this is a quick step 👍

@kuzhelov
Copy link
Contributor

kuzhelov commented Dec 13, 2018

just note aside - could you, please, suggest if you've had a chance to research the cause (source) of these TS warnings:

image

I mean, I see that those are produced by rollup's env, but just to understand which problem this is. Thanks!

@layershifter
Copy link
Member Author

I mean, I see that those are produced by rollup's env, but just to understand which problem this is.

This problem caused by TS helpers in the transpiled code, more details are there: rollup/rollup#794 (comment). I am not sure that we need to silence this warning, especially if we want to migrate to Babel.

@layershifter layershifter merged commit 81f97c4 into master Dec 14, 2018
@layershifter layershifter deleted the chore/reenable-project-test branch December 14, 2018 08:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants