Pavel
Pavel
Altough, even `.env` file doesn't work with your library on windows.
For those who on windows. Install `dotenv` and then add the config injection like this: ``` const contentfulManagement = require('contentful-management') require('dotenv').config() // space.getEnvironment(process.env.PRIVATE_CONTENTFUL_ENVIRONMENT_ID) ) } ```
Update. Component `Heading` throws the same issue. Probably, it's the reason.
I've experienced the issue with `@mui/material` and my own npm package `@gorazdo/tomui` The problem comes from a lot of modules to process (11k) like in [this article](https://dev.to/kyleapex/how-nextjs-12-improved-material-ui-app-compile-by-8x-47nf) Unfortunately, [this solution](https://github.com/vercel/next.js/discussions/17977#discussioncomment-2587974)...
To make it clearer, I have a couple of questions: 1. Does `gtm.js` add `gtag/js` automatically? (Looks like it is "yes", since gtm.js contains the `G-xxxxxx` key inside 2. Is...
After some digging, I realized the following issues with the current approach to query name generation. First, of all, I do believe the assumption of capitalizing and joining targets, sources,...
So, I came up with the following solution: 1. I copied the `providers` folder, kept only `buildDataProvider` and `AdminQueries.ts`, `Filter.ts`, `Pagination.ts`; 2. Created `utils.ts` file; 3. Modified `getQueryName` and `getQueryNameMany`...
This issue solves by upgrading to webpack v2.
I've done this for my project too, and it works well. So, I recommend you accept request into your repo. Thx.
The same and it's still not resolved. Also, for some reason I bumped to the issue of that all maps are `undefined` by default instead of empty Map objects, so...