You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest fresko version removed dependency to shelljs 馃殌
However, if one's project is relying on fresko to automatically run npm/yarn/pnpm install on a project that just got upgraded to latest fresko version (which happened @sline-io today), developers will run into this issue:
Error: Cannot find module '/XXX/node_modules/shelljs/src/exec-child.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
This is due to the fact that the fresko CLI currently running into the developer's terminal was still the version which had the dependency to shelljs - but during the CLI run the fresko dependencies changed - removing here the path to shelljs
Implementing a hot-reload feature into fresko would solve this issue, here's how it'd work:
fresko is ran using git hooks - will save it's package version in memory
each time a prompt's command is ran, we will check again if fresko package version changed
if package version got changed, fresko would exit & reload itself, using the new version that just got installed
optional: find a way to recover the CLI current state, to avoid re-starting the prompt sequence from the beginning
The text was updated successfully, but these errors were encountered:
Latest
fresko
version removed dependency toshelljs
馃殌However, if one's project is relying on
fresko
to automatically runnpm/yarn/pnpm install
on a project that just got upgraded to latestfresko
version (which happened @sline-io today), developers will run into this issue:This is due to the fact that the
fresko
CLI currently running into the developer's terminal was still the version which had the dependency toshelljs
- but during the CLI run thefresko
dependencies changed - removing here the path toshelljs
Implementing a hot-reload feature into
fresko
would solve this issue, here's how it'd work:fresko
is ran using git hooks - will save it's package version in memoryfresko
package version changedThe text was updated successfully, but these errors were encountered: