Closed tylersticka closed 6 years ago
@calebeby First priority should be diagnosis: Is this a simple dependency issue, does this require a big overhaul of the build process, etc.?
Possibly (probably?) related issue: cloudfour/core-gulp-tasks#63
@tylersticka the build seems to be working. Does it work for you?
Hmm...I also just tried this and it builds fine for me as well. π€
Steps I followed:
Jump into master
branch and pulled the latest
Ran npm start
Is that what wasn't working for you @tylersticka?
npm start
β¦ works! π node_modules
rm .nvmrc
nvm use node
(switches to v10.3.0
)npm start
againβ¦ also works! π Did you change anything? π€
@nicolemors Can you check to see if the problem is resolved for you, too?
π€·ββοΈ It seems to work even if I check out 5fdd23051392a9061c1a374915599f7f5493460c, which was before I made any changes.
@tylersticka @gerardo-rodriguez can we close this then?
@calebeby I think so.
@nicolemors If you encounter this again, please re-open and let us know what version of Node you're using.
Dependencies (both organizational and public) are way out of date. Default build fails as a result.
(Issue originally reported by @nicolemors)