Crimsonspell posted a new question

blog-module •

How to Build a Doctor Appointment App for Your Clinic

If your administrative staff spends hours scheduling appointments every day, you’re probably looking for a way to manage appointments more effectively. If you are, it’s reasonable to ask how the world’s top clinics go about solving this problem. And if you’re looking to develop a doctor appointment app, you’re in the right place. Today, we’ll talk about the benefits of this type of app, features to include, the cost of development, and success stories.


Crimsonspell posted a new question

blog-module •

How to Monetize Telemedicine Apps

App monetization is probably one of the most important things we can talk about when it comes to telemedicine app development. App owners look into different revenue streams to find their perfect model. But the tricky thing about choosing the right monetization strategy is that there isn’t a one-size-fits-all solution, especially in the healthcare niche. What works for others may not work for you.

No worries! We’ve prepared a guide that breaks down app monetization strategies by looking at some of the most popular names on the telemedicine market. Grab a cup of coffee and enjoy!


Crimsonspell posted a new question

blog-module •

How to Build an On-Demand Platform Like Uber or Airbnb

When we talk about building an on demand delivery app clone, we’re often talking about building an app like Uber or Airbnb. Two major decacorns (companies worth $10 billion or more), Uber and Airbnb are worth billions of dollars. To be more precise, Uber was valued at $72 billion and Airbnb at $29.3 billion as of August 2018. Uber is available in more than 65 countries and over 600 cities. Every day, nearly two million people rent accommodation through Airbnb. What’s so great about these two companies that makes so many people regularly use their applications and makes entrepreneurs want to copy them?

We’re in this article to talk about the philosophy behind an Uber- or Airbnb-like on-demand delivery service app.


Crimsonspell posted a new question

blog-module •

Accelerated Mobile Pages: What Is AMP and What Does It Mean for Your Mobile Business?

If you’ve ever searched for content and interacted with the results on a mobile device, you’ve probably encountered AMP, or Accelerated Mobile Pages. AMP is a good solution for websites that deal with huge volumes of data and need to retain fast performance. These can be informational websites, blogs, and news sites. For large projects, AMP can’t substitute for responsive or adaptive web design.

If you’re interested in using AMP or If you want a free consultation from our team, feel free to contact us. We’d be happy to help.


Crimsonspell posted a new question

blog-module •

Best mHealth Apps for Patients: Doctor-on-Demand

eHealth is an area that has seen a great deal of investment over the last couple of years, with medical mHealth Apps popping up left and right


Crimsonspell posted a new question

blog-module •

Video Chat App Development

People are switching to remote work due to the coronavirus quarantine. People are staying at home and can’t see their friends. This has led to a fast increase in the popularity of video chat apps. If you’re planning to develop a video chat app, now is the right time to start. Build immersive voice and video experiences with best video chat app development company


sthotakura posted a new question

blog-module •

(node:28176) DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead

I get this error when I add blog module to my nuxtjs app.

Here is the list of modules from my nuxt.config.js:

modules: [ '@nuxtjs/axios', '@nuxtjs/blog', ],

Dependencies from package.json:

"dependencies": { "@nuxtjs/axios": "^5.9.5", "@nuxtjs/blog": "0.0.1-6", "nuxt": "^2.0.0" },


jhd4tmr posted a new question

blog-module •

Not working for nuxt2.9.2

Nothing to preview


justindasilva posted a new question

blog-module •

Issue with Nuxt 2.8.0?

There seems to be an issue running this module with Nuxt 2.8.0

    throw new Error('Callback was already called.');

Error: Callback was already called.
    at throwError (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/neo-async/async.js:16:11)
    at /Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/neo-async/async.js:2818:7
    at Compilation.processModuleDependencies (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/Compilation.js:725:4)
    at afterBuild (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/Compilation.js:855:15)
    at buildModule.err (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/Compilation.js:899:11)
    at callback (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/Compilation.js:630:5)
    at (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/Compilation.js:678:12)
    at handleParseError (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/NormalModule.js:453:12)
    at doBuild.err (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/NormalModule.js:484:5)
    at runLoaders (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/lib/NormalModule.js:343:12)
    at /Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at Array.<anonymous> (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
    at provider (/Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/webpack/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9)
    at /Users/justin.dasilva/Sites/dev/justindasilva/web/node_modules/graceful-fs/graceful-fs.js:90:16
error Command failed with exit code 1.
info Visit for documentation about this command.

simonwjackson posted a new question

blog-module •

Broken after update to Nuxt 2
❯ npm run dev

> nuxt-blog-module-[email protected]1.0.0 dev /Users/simonwjackson/storage/code/sandbox/nuxt-blog-module-example
> nuxt

   blog:api Listening on /api/blog                                                                                                                                                17:05:11

 ERROR  Cannot destructure property createHash of 'undefined' or 'null'.                                                                                                        17:05:13

  at Object.<anonymous> (node_modules/extract-css-chunks-webpack-plugin/dist/index.js:27:5)
  at Module._compile (internal/modules/cjs/loader.js:689:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
  at Module.load (internal/modules/cjs/loader.js:599:32)
  at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
  at Function.Module._load (internal/modules/cjs/loader.js:530:3)
  at Module.require (internal/modules/cjs/loader.js:637:17)
  at require (internal/modules/cjs/helpers.js:20:18)
  at Object.<anonymous> (node_modules/extract-css-chunks-webpack-plugin/dist/cjs.js:3:18)
  at Module._compile (internal/modules/cjs/loader.js:689:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
  at Module.load (internal/modules/cjs/loader.js:599:32)
  at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
  at Function.Module._load (internal/modules/cjs/loader.js:530:3)
  at Module.require (internal/modules/cjs/loader.js:637:17)
  at require (internal/modules/cjs/helpers.js:20:18)

begueradj posted a new question

blog-module •


Does this support categories/tags?
Any conventions on how to write the .md files?


sangemi posted a new question

blog-module •

How to change default port

I start some app through some port.
package.json is like this.
"scripts": {
"dev": "nuxt -p=4400",

So after i installed blog module, i have to chage blog-module.js etc like this.

export default function NuxtModule(options) {
  const defaults = {
    base: 'http://localhost:4450',      <<<<<<<<<<<<<
    comments: false,

But this file is in node_modules directory.
Can i change above default port at nuxt.config.js ?


crstin posted a new question

blog-module •

Incompatible with nuxt 2.0
error TypeError: dep.getResourceIdentifier is not a function

bayssmekanique posted a new question

blog-module •

Support for static sites

This module works very well when I'm running in development mode, but when I go to generate a static site, there are a few issues that I've noticed.

  1. Navigating directly to a post via address works great, however, navigating to a post through any link makes a call to /api/blog/posts/{slug} which doesn't exist.
  2. Webpack does produce static JSON files which correspond to the /api/blog/posts/{slug} calls, but they are nested inside the public path directory (/_nuxt) and they have a .json extension added.
  3. The .json files are not versioned in any way. This is not a 100% deal breaker, since the corresponding .html files are no versioned either so they can share caching strategies, however it does go against the strategy of assuming everything in the pubilc path directory is versioned and thus can be cached for long periods.
  4. Blog routes do not appear to play well with the @nuxtjs/sitemap module and don't appear within the sitemap.xml file or the sitemap-routes.json file.

In the few days I've spent pulling apart code, I have not been able to figure out a way to resolve any of these issues, as this module is failry large and complex. I appreciate the capabilities but I don't know how useful it is without being able to function as a static file site. I'll continue to work on it as time allows but I would be very interested in knowing if there is some configuration that I'm missing that might make some of these pieces fall into place.


easherma posted a new question

blog-module •

Project status?

Is this actively being used or contributed to? Seems a little stale.


navarrorc posted a new question

blog-module •

Hello World example.

Can someone be kind enough to give me a hello world example? I don't know how to use the blog-module. Thanks in advanced.


adam-lynch posted a new question

blog-module •

Improve documentation

Could the documentation be improved please? This seems to be a lot more powerful than the README suggests but I'm not sure what the options do exactly or how I can customize the HTML outputted for each post preview, for example.


bskimball posted a new question

blog-module •

Npm run build fails

Nuxt rc11
Blog-module 0.0.1-6
on build Uglify fails

ERROR in 3.401771ae88b5828911b6.js from UglifyJs
Unexpected token: operator (>) [./node_modules/@nuxtjs/blog/src/app/mixins/api.js:7,0][3.401771ae88b5828911b6.js:111,20]

ERROR in 5.607bddffaeab0f9a14c9.js from UglifyJs
Unexpected token: operator (>) [./node_modules/@nuxtjs/blog/src/app/mixins/api.js:7,0][5.607bddffaeab0f9a14c9.js:100,20]

ERROR in 6.72fb925f626a18a70784.js from UglifyJs
Unexpected token punc «(», expected punc «:» [./node_modules/@nuxtjs/blog/src/app/mixins/collection.js:7,0][6.72fb925f626a18a70784.js:117,17]

ERROR in 7.d3452f4d13ebcec5cc93.js from UglifyJs
Unexpected token punc «(», expected punc «:» [./node_modules/@nuxtjs/blog/src/app/mixins/blog.js:6,0][7.d3452f4d13ebcec5cc93.js:77,17]

Looks like the code in the mixins is not run through babel before uglify tries to do what it needs to do, therefore is fails because it does not recognize the es6 arrow functions


greenkeeper[bot] posted a new question

blog-module •

Action required: Greenkeeper could not be activated 🚨

🚨 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, 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 integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.