v1.29.0

[mikecao]

Features

• You can now rename the default admin account
• Added CORS headers to all the website endpoints

Fixes

• Fixed XML error displaying in Firefox
• Fixed referrers being filtered incorrectly

Updates

• Language translation updates
• Upgraded Next.js to 12.1.4
• Upgraded Prisma to 3.11.1

A huge thanks to all the contributors on this release! 🙏@tycrek @RikoDEV @Kdecherf @SeesawLiu @Lemonawa @JeremDlcn

---

This discussion was created from the release v1.29.0.

[Lemonawa]

Awesome

[asbrwl]

Hi Mike,
I'm facing an issue when doing the NPM Install process with the new build on Node LTS on Ubuntu 20.04.
Node is installed through NVM.

Copying the error report also for your reference. Not sure if it is my system or the latest release as Umami 1.28 is working perfectly and as expected.

npm resolution error report

2022-04-04T09:10:13.804Z

While resolving: umami@1.29.0
Found: react@18.0.0
node_modules/react
react@"^18.0.0" from the root project

Could not resolve dependency:
peer react@"^16.3.0 || 17" from react-intl@5.24.8
node_modules/react-intl
react-intl@"^5.24.7" from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.
eresolve-report.txt

[mikecao]

Can you try pulling the latest v1.29.1?

[asbrwl]

Fixed and works!! Thanks for the awesome response

[brunoamaral]

Tried to update the docker-compose stack, and now I'm getting an error that the container can't find a command.

umami      | $ npm-run-all init start-app
umami      | /bin/sh: npm-run-all: not found
umami      | error Command failed with exit code 127.

[mikecao]

Can you try pulling the latest v1.29.1?

[brunoamaral]

Just did and seems to be working 🙂
The frontend still shows 1.29.0 though

[H0rn0chse]

Thanks for the update 🚀
I've just upgrade my umami hosted on heroku to v1.29.x and got similar errors like already reported
I've tested v1.29.1 and v1.29.2?
But I'm still getting internal server errors:

2022-04-04T11:36:31.595378+00:00 app[web.1]: TypeError: (0 , react_jsx_dev_runtime__WEBPACK_IMPORTED_MODULE_0__.jsxDEV) is not a function
2022-04-04T11:36:31.595388+00:00 app[web.1]:     at App (webpack-internal:///./pages/_app.js:69:96)
2022-04-04T11:36:31.595389+00:00 app[web.1]:     at d (/app/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:33:498)
2022-04-04T11:36:31.595389+00:00 app[web.1]:     at bb (/app/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:36:16)
2022-04-04T11:36:31.595394+00:00 app[web.1]:     at a.b.render (/app/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:42:43)
2022-04-04T11:36:31.595394+00:00 app[web.1]:     at a.b.read (/app/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:41:83)
2022-04-04T11:36:31.595395+00:00 app[web.1]:     at Object.exports.renderToString (/app/node_modules/react-dom/cjs/react-dom-server.node.production.min.js:52:138)
2022-04-04T11:36:31.595396+00:00 app[web.1]:     at Object.renderPage (/app/node_modules/next/dist/server/render.js:768:45)
2022-04-04T11:36:31.595396+00:00 app[web.1]:     at Object.defaultGetInitialProps (/app/node_modules/next/dist/server/render.js:375:51)
2022-04-04T11:36:31.595396+00:00 app[web.1]:     at Function.getInitialProps (webpack-internal:///./node_modules/next/dist/pages/_document.js:173:20)
2022-04-04T11:36:31.595397+00:00 app[web.1]:     at Object.loadGetInitialProps (/app/node_modules/next/dist/shared/lib/utils.js:65:29)

[mikecao]

Does this help? https://stackoverflow.com/questions/67376052/error-when-running-next-js-typeerror-0-react-jsx-dev-runtime-webpack-impo

[H0rn0chse]

I've set NODE_ENV to production which didn't help
afterwards I've tested development which did something
Now I'm getting an error on the Browser:

Unhandled Runtime Error
TypeError: anchorElement is null
Call Stack
options.insert
webpack-internal:///./styles/variables.css (16:34)
insertStyleElement
webpack-internal:///./node_modules/next/dist/build/webpack/loaders/next-style-loader/runtime/injectStylesIntoStyleTag.js (91:17)
addStyle
webpack-internal:///./node_modules/next/dist/build/webpack/loaders/next-style-loader/runtime/injectStylesIntoStyleTag.js (167:17)
modulesToDom
webpack-internal:///./node_modules/next/dist/build/webpack/loaders/next-style-loader/runtime/injectStylesIntoStyleTag.js (69:26)
module.exports
webpack-internal:///./node_modules/next/dist/build/webpack/loaders/next-style-loader/runtime/injectStylesIntoStyleTag.js (193:39)
<unknown>
webpack-internal:///./styles/variables.css (25:17)
./styles/variables.css
file:/app/.next/static/chunks/pages/_app.js (9417:1)
options.factory
/_next/static/chunks/webpack.js (606:31)
__webpack_require__
file:/app/.next/static/chunks/webpack.js (37:33)
fn
/_next/static/chunks/webpack.js (275:21)
<unknown>
webpack-internal:///./pages/_app.js (15:97)
./pages/_app.js
file:/app/.next/static/chunks/pages/_app.js (9505:1)
options.factory
/_next/static/chunks/webpack.js (606:31)
__webpack_require__
file:/app/.next/static/chunks/webpack.js (37:33)
fn
/_next/static/chunks/webpack.js (275:21)
<unknown>
webpack-internal:///./node_modules/next/dist/build/webpack/loaders/next-client-pages-loader.js (5:16)
onEntrypoint/<
webpack-internal:///./node_modules/next/dist/client/route-loader.js (221:24)

Redeploying/ building v1.28.0 still works for me.

[H0rn0chse]

@mikecao
I've found that reverting the dependency next to 12.1.0 fixes the issue as well. Once I bump the version to 12.1.1 or higher the issues reoccur. I'm currently doing further investigations on the root issue.

[lxndrblz]

@H0rn0chse I am getting the same error, since updating to any version beyond v1.28.0. Did you find a solution?

[H0rn0chse]

Not yet
I'm following this issue:
#1071

[hemorej]

My app fails to start, there's not much in the logs but it seems unhappy with the beta Middleware. What's the minimum node version we need now, has this changed ?
I'm running this on a DO droplet

[mikecao]

Are you pulling from the repo or docker?

[hemorej]

@mikecao from the repo. It did have trouble resolving some react related dependencies, so I thought I should update node, the npm install step seems to have worked but the server wouldn't start, kept getting a redirect loop

[hemorej]

@mikecao still not building for me. Just tried the latest release, same problem. This is with npm@8.6.0 doing a build-app

info  - Loaded env from /var/www/html/.env
(node:1695) ExperimentalWarning: The ESM module loader is experimental.
info  - Checking validity of types  
warn  - using beta Middleware (not covered by semver) - https://nextjs.org/docs/messages/beta-middleware
info  - Creating an optimized production build  
info  - Compiled successfully
info  - Collecting page data .(node:1740) ExperimentalWarning: The ESM module loader is experimental.
(node:1695) UnhandledPromiseRejectionWarning: file:///var/www/html/node_modules/zustand/esm/index.mjs:1
import { useReducer, useRef, useDebugValue, useEffect, useLayoutEffect } from 'react';
                     ^^^^^^
SyntaxError: The requested module 'react' is expected to be of type CommonJS, which does not support named exports. CommonJS modules can be imported by importing the default export.
For example:
import pkg from 'react';
const { useReducer, useRef, useDebugValue, useEffect, useLayoutEffect } = pkg;
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:97:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:136:20)
    at async Loader.import (internal/modules/esm/loader.js:179:24)
(node:1695) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1695) [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.
(node:1695) UnhandledPromiseRejectionWarning: file:///var/www/html/node_modules/zustand/esm/index.mjs:1
import { useReducer, useRef, useDebugValue, useEffect, useLayoutEffect } from 'react';
                     ^^^^^^
SyntaxError: The requested module 'react' is expected to be of type CommonJS, which does not support named exports. CommonJS modules can be imported by importing the default export.
For example:
import pkg from 'react';
const { useReducer, useRef, useDebugValue, useEffect, useLayoutEffect } = pkg;
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:97:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:136:20)
    at async Loader.import (internal/modules/esm/loader.js:179:24)
(node:1695) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

> Build error occurred
file:///var/www/html/node_modules/zustand/esm/index.mjs:1
import { useReducer, useRef, useDebugValue, useEffect, useLayoutEffect } from 'react';
                     ^^^^^^
SyntaxError: The requested module 'react' is expected to be of type CommonJS, which does not support named exports. CommonJS modules can be imported by importing the default export.
For example:
import pkg from 'react';
const { useReducer, useRef, useDebugValue, useEffect, useLayoutEffect } = pkg;
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:97:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:136:20)
    at async Loader.import (internal/modules/esm/loader.js:179:24) {
  type: 'SyntaxError'
}