n6g7 / httpdf Goto Github PK

Hi,

I cloned your project, did 'yarn install' and then 'yarn dev' and I am getting errors like this:

Error: Cannot find module './../.build/asyncProps.js'
Error: Cannot find module './../.build/broken.js'
Error: Cannot find module './../.build/demo.js'
Error: Cannot find module './../.build/components/index.js'

Could you help me to fix this problem and make it work?

Return array of errors for each prop instead of strings.

For faster development (no need to rebuild image when changing files).

Ideas:

• create new HTTPDF_DEBUG env var. following behaviour only applies when set to true (defaults to false)
• watch $HTTPDF_DOCUMENTS_SRC for changes
• on change:
  • recompile files (using babel)
  • re-run resolver.buildIndex()
  • print some sort of message to let user know files were reloaded
  • ...
  • profit

Provide example of tests to test validity of JS files before babel transpilation.

Dependabot couldn't find a package.json for this project.

Dependabot requires a package.json to evaluate your project's current JavaScript dependencies. It had expected to find one at the path: /lib/js/package.json.

If this isn't a JavaScript project, or if it is a library, you may wish to disable updates for it from within Dependabot.

You can mention @dependabot in the comments below to contact the Dependabot team.

Goal: to make designing files easier.

Adding ?debug to a url would return HTML instead of a pdf.
With inline css, etc.

Bonus: hot reloading?

Components are rendered synchronously which means we can't do any async processing before rendering a file.

We could support a pre-render async method in the component class which could return initial props (à la getInitialProps).

class Test extends PureComponent {
  static document = true

  static async getInitialProps(props) {
     return {
      ...props,
      api: await myApi()
    }
  }

  render() {
    ...
  }
}

Use alpine base?
https://antonfisher.com/posts/2018/03/19/reducing-docker-image-size-of-a-node-js-application/

Thanks for providing the container! I have a question about one httpd config:AuthnCacheContext.
It seems the official document recommends to change the default directory, which is conservative and not optimal. A better policy is to name the AuthnCacheContext for the password provider: for example a htpasswd file or database table.

Maybe it's better to set that to specify a context string for use in the cache keyin the comfig file? Thanks.

Users can't add custom node dependencies (eg. moment, luxon, etc).
Current solution: add a yarn add command to Dockerfile.

Don't want to provide an URL to render every component in the tree.

The docker container crashes on me, with the node process being killed.

This happened while running v0.0.6 on AWS ECS using 256 MB of memory.

Do images work out of the box? 🤔

Hi,

This is a fantastic microservice. I have been trying to setup my own docker but am having issues with CORS. Things I have attempt:

1. Add cors npm package and follow setup process
   -I would have thought this would solve any issues, but Im not sure if there is something odd happening during the indexing process that creates the routes.

2. Using Moseif CORS extension on chrome, this works but I cant ask people to download it =)

Any tips to get rid of "has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."?