This channel is not moderated by Netlify staff. For staff and peer support, please head to 👉 community.netlify.com
serum I can't seem to find anything in the docs / API
5:17:35 PM: Different build dir detected, going to use the one specified in the Netlify configuration file: 'frontend' versus '' in the Netlify UI
5:17:35 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'frontend/build' versus 'build/' in the Netlify UI
5:17:35 PM: Starting build script
5:17:35 PM: Installing dependencies
5:17:35 PM: Python version set to 2.7
5:17:36 PM: Downloading and installing node v10.21.0...
5:17:36 PM: Downloading https://nodejs.org/dist/v10.21.0/node-v10.21.0-linux-x64.tar.xz...
5:17:37 PM: Computing checksum with sha256sum
5:17:37 PM: Checksums matched!
5:17:39 PM: Now using node v10.21.0 (npm v6.14.4)
5:17:39 PM: Started restoring cached build plugins
5:17:39 PM: Finished restoring cached build plugins
5:17:39 PM: Attempting ruby version 2.6.2, read from environment
5:17:40 PM: Using ruby version 2.6.2
5:17:41 PM: Using PHP version 5.6
5:17:41 PM: 5.2 is already installed.
5:17:41 PM: Using Swift version 5.2
5:17:41 PM: Started restoring cached node modules
5:17:41 PM: Finished restoring cached node modules
5:17:41 PM: Installing NPM modules using NPM version 6.14.4
5:17:59 PM: npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142
5:18:00 PM: npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
5:18:23 PM: npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. 5:19:07 PM: npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. 5:19:09 PM: npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 5:19:13 PM: npm WARN deprecated core-js@1.2.7: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. 5:19:25 PM: npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. 5:19:47 PM: npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated 5:19:49 PM: npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated 5:19:50 PM: npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart() 5:21:15 PM: > grpc@1.23.3 install /opt/build/repo/frontend/node_modules/grpc
5:21:15 PM: > node-pre-gyp install --fallback-to-build --library=static_library
5:21:15 PM: node-pre-gyp WARN Using request for node-pre-gyp https download
5:21:16 PM: [grpc] Success: "/opt/build/repo/frontend/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node" is installed via remote
5:21:16 PM: > puppeteer@1.20.0 install /opt/build/repo/frontend/node_modules/puppeteer
5:21:16 PM: > node install.js
5:21:23 PM: Chromium downloaded to /opt/build/repo/frontend/node_modules/puppeteer/.local-chromium/linux-686378
5:21:23 PM: > core-js@3.2.1 postinstall /opt/build/repo/frontend/node_modules/@firebase/polyfill/node_modules/core-js
5:21:23 PM: > node scripts/postinstall || echo "ignore"
5:21:23 PM: > core-js@2.6.11 postinstall /opt/build/repo/frontend/node_modules/core-js
5:21:23 PM: > node -e "try{require('./postinstall')}catch(e){}"
5:21:24 PM: > core-js-pure@3.6.5 postinstall /opt/build/repo/frontend/node_modules/core-js-pure
5:21:24 PM: > node -e "try{require('./postinstall')}catch(e){}"
5:21:24 PM: > core-js@3.6.5 postinstall /opt/build/repo/frontend/node_modules/plyr/node_modules/core-js
5:21:24 PM: > node -e "try{require('./postinstall')}catch(e){}"
5:21:24 PM: > protobufjs@6.9.0 postinstall /opt/build/repo/frontend/node_modules/protobufjs
5:21:24 PM: > node scripts/postinstall
5:21:24 PM: > core-js@3.6.5 postinstall /opt/build/repo/frontend/node_m
2 replies
after hugo runs in the logs, I see
Failed to get JSON resource "https://xxx.netlify.app/how-to/python/notebook-test/testnotebook.ipynb": Failed to retrieve remote file: Unauthorizedif i visit the url, it is there and loads as json file... I am wondering why is that error happening and I am a little flabbergasted.
adan_geno Hi every body,
check out this new platform wirtten in Angluar
j7c5 > <@gitter_akshitkrnagpal:matrix.org> Hi all.
I am trying to configure my Netlify project like this. Every time I push code to the repo it gets automatically deployed and published on next.domain.com and when I trigger manually it get published on domain.com. Can anyone give me some idea how to do this?
I believe that deploy context is Netlify's mechanism to handle this in a single deployment, however, I do this with two site deployments and two GitHub branches. Deploy the domain.com from the master branch and add your domain alias to domain.com and www.domain.com. Create a new site deployed from the dev branch of your repo and add your subdomain alias next.domain.com and www.next.domain.com. Then, work in the dev branch and when you push it to your repo Netlify will auto build and you can preview it. When you are ready to update your main page you create a pull request and merge, and this will auto trigger a build on domain.com. That’s how I do it.
getting this error, no changes
Version '10' not found - try nvm ls-remote to browse available versions.
but still not sure how a cloudflare issue, and i for sure know 10 is a valid value
I could not deploy my production. status is building since yesterday. this site is simple static contents.
deploy log is end with this.
6:47:43 PM: Preparing Git Reference refs/heads/master
6:47:44 PM: No build command found, continuing to publishing
6:47:45 PM: Finished processing build request in 2.982765884sIs there something that is considered to be the cause of that?
Anyone seen this kind of error in the CMS admin UI before?
react_devtools_backend.js:2430 TypeError: Failed to fetch
{type: "ENTRIES_FAILURE", error: "Failed to load entries", payload: "TypeError: Failed to fetch", meta: {…}}
error: "Failed to load entries"
meta: {collection: "config"}
payload: "TypeError: Failed to fetch"
type: "ENTRIES_FAILURE"
__proto__: Object
Step to host site:
1) Add to archive files css folder, img folder and index.html.
2) Upload the archive to Netify
3) Open the site URL
ACT>> page not found message((
logs from deploy details.
12:38:15 PM: Creating deploy upload records
12:38:15 PM: Starting post processing
12:38:15 PM: Post processing - HTML
12:38:15 PM: Post processing - header rules
12:38:16 PM: Post processing - redirect rules
12:38:16 PM: Post processing done
12:38:16 PM: Site is live ✨
deankayton How everyone. Can anyone see what is wrong with my admin/config.yml? It doesn't produce the correct filename as I would expect (it always creates a .md file, so it is as if the slug does not exist at all).
https://gitlab.com/dnk8n/research_db_docs/-/blob/master/mkdocs/docs/admin/config.yml
You can see by history I have tried many things.
Anyone else had this error with ncms.
Warning: Failed prop type: invariant is not defined
at x (http://localhost:3000/_next/static/chunks/1.js:468:66487)
at l (http://localhost:3000/_next/static/chunks/1.js:460:53996)
at http://localhost:3000/_next/static/chunks/1.js:426:189812
at Connect(Component) (http://localhost:3000/_next/static/chunks/1.js:305:26272)
at c (http://localhost:3000/_next/static/chunks/1.js:305:24194)I'm totally loast as to how to debug this efficiently given everything is obscured/minified.
Hi, I'm using Netlify functions to send aws ses emails. The function fires locally perfectly and I get the email as expected but once I get this into production or into build the email does not get sent the first time but upon trying again it sends the previous email that I should have got, it feels like the functions fire but they are out of step and only ever sends the previous request not that current request.
The gist is that a user enters their email, it sends the email to the lambda function, we then check it and send an AWS email with a magic sign in link to that email. Like I said above locally fine works as normal but in build env it only fires the second time and it is a step out each time
(nextjs,custom widget) So, cms custom widget editor, i register a custom editor widget with cms.registerEditorComponent(BannerBlockEditorComponent); in its toPreview i return 'return <BannerBlock data={obj}></BannerBlock>' where banner block is basically a div with a button and an useCallback handler.
In the cms preview the buttons callback doesn't work. So my question is, is it? or should it be possible to have a custom components javascript work? Its like the javascript for the preview iframe isn't being embedded.
