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
I have searched existing issues to ensure the feature has not already been requested
🚀 Feature Proposal
it's unintuitive (for me at least) to have to imperatively declare --esm to fastify eject when using js/esm combination.
Like, when I'm already cd-ed into the dir, and eject is using process.cwd(), meaning it can also lookup pkg json and see what's there.
other point is that scripts stay bound to CLI, I expect to have scripts overwritten to something like "start" : "node server.js" | "dev" : "node --watch server.js" at least in js case.
bonus points if CLI would have removed itself from dependencies, and dumped that test helper into tests directory
Motivation
I don't have to massage the generated project too much after eject
Example
No response
The text was updated successfully, but these errors were encountered:
Prerequisites
🚀 Feature Proposal
it's unintuitive (for me at least) to have to imperatively declare
--esm
tofastify eject
when using js/esm combination.Like, when I'm already cd-ed into the dir, and eject is using
process.cwd()
, meaning it can also lookup pkg json and see what's there.other point is that scripts stay bound to CLI, I expect to have scripts overwritten to something like
"start" : "node server.js"
|"dev" : "node --watch server.js"
at least in js case.bonus points if CLI would have removed itself from dependencies, and dumped that test helper into tests directory
Motivation
I don't have to massage the generated project too much after
eject
Example
No response
The text was updated successfully, but these errors were encountered: