fmiras / next-pkg Goto Github PK

When installing next-pkg and running the npm run dist which we suggest from the README.md isn't going to work unless the user runs next build we should warn/ask to build the project before compiling with pkg.

./next-express-bootstrap-boilerplate
/snapshot/frontend/node_modules/next-server/dist/server/next-server.js:271
throw new Error(Could not find a valid build in the '${this.distDir}' directory! Try building your app with 'next build' before starting the server.);

after packaging my app and try running it , i run into an error
`- error Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error
/snapshot/next-sample/node_modules/next/dist/server/config.js:546
userConfigModule = await import((0, _url.pathToFileURL)(path).href);
^

TypeError: Invalid host defined options
at loadConfig (/snapshot/next-sample/node_modules/next/dist/server/config.js:546:78)
at async Proxy. (/snapshot/next-sample/node_modules/next/dist/server/next.js:260:44)
`
Thing i have tried are:

• everything works fine when i run in dev mode
• when i build and 'next start', it also works fine
• start a new next project - still encounter same error
• when i remove the next-config.js - it works but then i run into eslint problems

Works if I hack the dist/index.js to point at server/index.js instead of ../lib/server.js.

Haven't looked any deeper.

When using next-pkg on windows, dist file requires to be on same path as .next compiled sources. It should be independent of it's location and also file self-dependent

Hi there, have you had an idea of this?

vercel/pkg#694

Thanks
Carlos Vieira

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

hello...
I'm using this boiler plalate

sudo npm run dist

[email protected] dist /home/shintaro/Desktop/projects/github/frontend
next-pkg

✖ Error copying temporary files: Error: ENOENT: no such file or directory, stat '/home/shintaro/Desktop/projects/github/frontend/node_modules/next-pkg/lib/server.js'
(node:12322) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, stat '/home/shintaro/Desktop/projects/github/frontend/node_modules/next-pkg/lib/server.js'
(node:12322) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:12322) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Hi, my "dev" command doesn't follow the conventional "next" pattern shown in your documentation and instead I run "node server.js". Will next-pkg work with such a setup or is it totally incompatible?

const port = parseInt(process.env.PORT, 10) || 3000
const dev = process.env.NODE_ENV !== 'production'

const { createServer } = require('http')
const { parse } = require('url')
const next = require('next')
const mobxreact = require('mobx-react')
const app = next({ dev })
const handle = app.getRequestHandler()

mobxreact.useStaticRendering(true)

console.log("process.cwd() = " + process.cwd());

app.prepare().then(() => {
  createServer((req, res) => {
    const parsedUrl = parse(req.url, true)
    const { pathname, query = {} } = parsedUrl;
    if(pathname.includes("/static/") || pathname.includes("/_next/")){
      handle(req, res, parsedUrl)
    }else{
      query.path=pathname
      app.render(req, res, '/', query)
    }

  }).listen(port, err => {
    if (err) throw err
    console.log(`> Ready on http://localhost:${port}`)
  })
})

"scripts": {
    "dev": "node server.js",
    "build": "next build",
    "start": "NODE_ENV=production node server.js",
    "dist": "next-pkg"
  },

after packaging my app and try running it , i run into an error
`- error Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error
/snapshot/next-sample/node_modules/next/dist/server/config.js:546
userConfigModule = await import((0, _url.pathToFileURL)(path).href);
^

TypeError: Invalid host defined options
at loadConfig (/snapshot/next-sample/node_modules/next/dist/server/config.js:546:78)
at async Proxy. (/snapshot/next-sample/node_modules/next/dist/server/next.js:260:44)
`
Thing i have tried are:

• everything works fine when i run in dev mode
• when i build and 'next start', it also works fine
• start a new next project - still encounter same error
• when i remove the next-config.js - it works but then i run into eslint problems

Next-Pkg should support package.json pkg configuration as same as pkg does (for example, with assets and scripts properties).

  "pkg": {
    "scripts": "build/**/*.js",
    "assets": "views/**/*"
  }

We should support usage of custom next.js server with next-pkg dist script, maybe reading package.json start script so developers don't need to use pkg manually.

Next-Pkg cli package should accepto pkg cli arguments such as --target or --output using the exec exported function:

await exec([ 'app.js', '--target', 'host', '--output', 'app.exe' ])
// do something with app.exe, run, test, upload, deploy, etc

Hello folks,

i'm currently trying to deploy an nextjs application to a windows embedded pc. so l would like to have a complete bundled application.
I've got an exe file out with pkg, but if i start it, it closes immediatly without any errors.

I've also tried it with next-pkg, but it wont work either. so is next-pkg still state of the art or is there a other working way?

I want to target another platform that's not host.

const execution = exec([
      finalServerPath,
      '--target',
      'host',
      '--output',
      `${binaryFilePath}`
    ])