The concept of remix setup node seems to break the way npm is intended to work

[knpwrs]

See #205

Using the default remix templates, running npm ci when NODE_ENV=production, or when using the --production flag, installation fails because the postinstall hook contains remix setup node, and remix comes from @remix-run/dev, which is, by default, a devDependency. I looked into what the remix setup node command was doing, and while I don't completely understand it, it seems to break the way npm is intended to work. Would these steps be better suited to a build step or similar?

Thoughts?

How does the remix team suggest building production Docker images? Install with dev dependencies? Move @remix-run/dev to a regular dependency?