Question: how can I know? or how to fix it?

Asked By
cdzos97
Asked At
2017-11-13 11:19:51

Found 15 possible answers.

User Answered At Possible Answer
sven 2017-11-13 11:20:40 CI is ok The test is maybe flaky on your machine
cdzos97 2017-11-13 11:23:41 Eh, I havn't push the commits, wait a minute.
sven 2017-11-13 11:24:19 Ok, I was looking at the last build
cdzos97 2017-11-13 11:24:46 Ok
sven 2017-11-13 11:30:08 Just resolved the conflicts inside your branch but it seems that the last build passed
cdzos97 2017-11-13 11:34:18 It failed. :joy:
sven 2017-11-13 11:34:37 Error: ENOENT: no such file or directory, scandir '/home/ubuntu/babel/packages/babel-plugin-proposal-pattern-matching/test/fixtures'
cdzos97 2017-11-13 11:36:32 Oh, got it.
sven 2017-11-13 11:36:55 Seems like you're missing the fixtures folder. Do you have the same issue locally or only CI?
cdzos97 2017-11-13 11:37:52 Only CI. But I am trying to pull the merged version and build again Thanks
hzoo 2017-11-13 16:54:43 based on https://github.com/babel/babel/pull/6789 what is our actually default now @loganfsmyth ? and what are we msising with https://github.com/babel/babel/issues/6242 now in the babel-core docs the default says module but you changed it to say default to script in babylon?
hulkish 2017-11-13 17:10:36 hi @hzoo @thecodedestroyer.. while his migration guide is extremely helpful: https://babeljs.io/blog/2017/09/12/planning-for-7.0
hzoo 2017-11-13 17:10:56 its not complete it's hard to do it i'm still trying to write what the changes are
hulkish 2017-11-13 17:11:24 i was hoping you guys might help me form a complete list of babel plugins/presets which have breaking changes (the package name change aside)
hzoo 2017-11-13 17:11:37 all the packages are the one in the monorepo?

Related Questions